I see in 2.0 changes that it
/Fixed a problem where ACCEPT_SET would wait for the corresponding 
MOVE_SET or FAILOVER_SET to arrive while holding an exclusive lock on 
sl_config_lock, preventing the other remote worker to process that event.
/
Does it mean that we should migrate to 2.0 to fix the bug we met ?

Thx

Cyril SCETBON wrote:
> Hi guys,
>
> We're using Slony 1.2.15 and met this error. It was announced that a 
> bug was fixed by a *Yoshiharu Mori*'s patch but we got this error 
> during 1 day and the replication was not working anymore. We had to 
> drop and readd the node to fix it.
>
> Anything else about this error ?
>

-- 
Cyril SCETBON