Bruno Wolff III <bruno@wolff.to> writes:
> Richard Lough <ralough.ced@dnet.co.uk> wrote:
>> I find that the update to table A attempts to produce a duplicate
>> primary primary key, and synchronisation with the server is lost.
> I don't think it is normal for failed update statements to cause loss
> of synchronization with the server.
It is not. And if that is what is happening, how does the second update
"proceed" at all? I suspect client-side programming error, but there's
not enough info here to diagnose it.
regards, tom lane
