Wed Jul 6 08:41:48 PDT 2011
- Previous message: [Slony1-bugs] [Bug 218] slon often has to retry transactions due to concurrent update in 2.1.0.b2
- Next message: [Slony1-bugs] [Bug 223] slonik can wait for a node it just uninstalled
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=218 --- Comment #18 from Christopher Browne <cbbrowne at ca.afilias.info> 2011-07-06 08:41:48 PDT --- (In reply to comment #16) > in cleanupThread.c there is no explicit transaction (that I can see) > > This means that the LOCK TABLE a and the 'select ..cleanupEvent(...) are done > in separate transactions, so the lock is already released before the call to > cleanupEvent. Eek, yes, that's doubtless so. There wasn't an explicit transaction because the cleanup thread used to have, as a major component, running VACUUM against Slony's tables, and that can't take place inside a transaction. We clearly have activity that needs a transaction, so this needs to complicate a little bit. -- 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.
- Previous message: [Slony1-bugs] [Bug 218] slon often has to retry transactions due to concurrent update in 2.1.0.b2
- Next message: [Slony1-bugs] [Bug 223] slonik can wait for a node it just uninstalled
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list