Obtaining this lock actually increases deadlock because
it creates a conflict between sl_config_lock and sl_event_lock.

slonik initiated queries will always obtain sl_event_lock before
sl_config_lock (or at least when creating events).  Having
remote_worker do the opposite isn't a good idea.

If we find more examples of deadlock with this removed then
they need to be adressed in some other fashion.

Branch
------
master

Details
-------
http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=a0729b759306dd21fe4043ee52a80fae5b515c90

Modified Files
--------------
src/slon/remote_worker.c |   11 +----------
1 files changed, 1 insertions(+), 10 deletions(-)