From: Koichi S. <koi...@gm...> - 2014-02-27 02:43:50
|
I may be wrong. The key issue is XC planner may choose CTID as a key to update/delete replicated table rows when whole statement cannot push down to datanodes. I understood this was introduced in 1.2 but this could have been an issue in 1.1 as well. Ashutosh, Abbas, could you clarify this? Regards; --- Koichi Suzuki 2014-02-19 4:46 GMT+09:00 David E. Wheeler <da...@ju...>: > On Feb 16, 2014, at 11:13 PM, 鈴木 幸市 <ko...@in...> wrote: > >> 1.1 is not suffered by this. The bug was introduced during planner code change to deal with PG planner code change (mainly from automatic updatable views). > > I don’t understand. I get this error on 1.1, and Abbas says it is not present in 1.2. That seems like an issue in 1.1 that might be fixable in a 1.1.1 release, should there ever be one. Am I missing something? > > Best, > > David > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers |