Re: [Postgres-xc-developers] Replicated update and delete

[Michael P. <mic...@gm...>]

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...
-- 
Michael