From: Amit K. <ami...@en...> - 2013-11-06 06:34:56
|
On 6 November 2013 09:55, Michael Paquier <mic...@gm...> wrote: > On Wed, Nov 6, 2013 at 11:00 AM, Koichi Suzuki <koi...@gm...> > wrote: > > I'm thinking to correct trigger implementation to use primary key or > "unique > > and not null" columns. As you suggested, this could be a serious > problem. > > I found that CTID can be different very easily in replicated tables and > it > > is very dangerous to use current CTID to identify tuples. , > This looks like an approach close to what is recommended for FDWs in > the Postgres docs, where a primary key should be used to scan foreign > tuples, primarily for writable APIs. So yes it might be the way to > go... > I won't have bandwidth to review the patch itself. But just a few questions : What exactly does the PostgreSQL FDW doc say about updates and primary key ? How does the postgres_fdw update a table that has no primary or unique key ? In the patch, what do we do when the replicated table has no unique/primary key ? -- > Michael > > > ------------------------------------------------------------------------------ > November Webinars for C, C++, Fortran Developers > Accelerate application performance with scalable programming models. > Explore > techniques for threading, error checking, porting, and tuning. Get the most > from the latest Intel processors and coprocessors. See abstracts and > register > http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > |