On 1/30/2013 9:55 AM, bugzilla-daemon at main.slony.info wrote:

> The UPDATE to sl_setsync does not have ssy_origin as part of the where clause,
> because we are running in READ COMMITTED mode the DELETE+INSERT of the row on
> sl_setsync becomes visible to the UPDATE part of sync_event() even though the
> sync_event() started before the ACCEPT_SET was processed.

This sounds very plausible.

I wonder if Slony in general is using too many concurrent threads. 
Unfortunately changing that won't be easy.


Jan

-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin