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

--- Comment #6 from Jan Wieck <janwieck at yahoo.com> 2011-06-09 11:56:45 PDT ---
Does this actually solve the problem or does it only lower the chance of
running into it?

You remember we had the discussion about LOCK TABLE with respect to snapshots
and realized, that LOCK TABLE statements at the beginning of a transaction
actually cause the lock to be taken out BEFORE the transaction snapshot is
generated. However, this LOCK TABLE cannot be done from inside of a stored
procedure because SELECTing that SP causes the snapshot to be generated before
the LOCK TABLE statement itself.

My gut feeling is that we need slonik to do the LOCK on the sl_config_log at
the beginning of any transaction, where it intends to call SPs that change the
configuration.


Jan

-- 
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.