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

--- Comment #2 from Steve Singer <ssinger at ca.afilias.info> 2011-06-08 08:54:41 PDT ---

The answer to my previous question is in the PostgreSQL documentation for 'lock
table'
----------
To achieve a similar effect when running a transaction at the Serializable
isolation level, you have to execute the LOCK TABLE statement before executing
any SELECT or data modification statement. A serializable transaction's view of
data will be frozen when its first SELECT or data modification statement
begins. A LOCK TABLE later in the transaction will still prevent concurrent
writes — but it won't ensure that what the transaction reads corresponds to the
latest committed values. 
-----------------

We should move the lock table on sl_config_lock to be outside of the
storePath_int call, similar to what we did for sl_event_lock.

-- 
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.
You are the assignee for the bug.