http://www.slony.info/bugzilla/show_bug.cgi?id=218

--- Comment #9 from Steve Singer <ssinger at ca.afilias.info> 2011-06-09 12:29:27 PDT ---
(In reply to comment #8)
> For what release would you consider that?

I see no reason to fix this in 2.0.

In 2.1 we removed the 'lock sl_config_lock' at the top of the slon remote
worker thread, we  did this because it could cause deadlocks with the
sl_event_lock that slonik now obtains.   An argument can be made that since we
are messing with locking behaviour in 2.1 anyway, and some of our chances
exposed some of the behaviour issues under testing then we should properly fix
the problem in 2.1 

Thoughts?

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.