Tue May 17 10:07:56 PDT 2011
- Previous message: [Slony1-bugs] [Bug 213] New: failover while slon is not running
- Next message: [Slony1-bugs] [Bug 214] New: Slonikconfdump.sh lost
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=137 --- Comment #7 from Christopher Browne <cbbrowne at ca.afilias.info> 2011-05-17 10:07:56 PDT --- After discussion with Marko Kreen and Jan Wieck, it should not be necessary to split off the LOCK statements from the DDL. If it's needful to lock tables in particular order to evade deadlock, that is dealt with by putting LOCK requests into the DDL script. But by running each statement immediately before logging into sl_log_{1,2}, that imposes all necessary locks in an order that protects from race conditions. -- 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 213] New: failover while slon is not running
- Next message: [Slony1-bugs] [Bug 214] New: Slonikconfdump.sh lost
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list