Wed Mar 2 10:04:47 PST 2011
- Previous message: [Slony1-bugs] [Bug 196] snapshot id values appear to travel backwards in sl_event
- Next message: [Slony1-bugs] [Bug 196] snapshot id values appear to travel backwards in sl_event
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=196 --- Comment #3 from Christopher Browne <cbbrowne at ca.afilias.info> 2011-03-02 10:04:46 PST --- OK, updated to expressly submit LOCK TABLE sl_event_lock, rather than allowing race condition by doing it inside a stored function. There a few more places to adjust, as there are stored functions that generate events: a) failednode2() generates an event, so the table needs to be locked before calling this function in src/slonik/slonik.c b) failoverSet_int() generates an event, hence src/slon/remote_worker.c needs to lock the table first. https://github.com/cbbrowne/slony1-engine/commit/215054a2ff4f3833aec9cd7f39fcb45a1ee00455 It has been speculated that there's an event created as part of subscription that needs to be guarded; I still need to seek that out, if it exists. -- 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 196] snapshot id values appear to travel backwards in sl_event
- Next message: [Slony1-bugs] [Bug 196] snapshot id values appear to travel backwards in sl_event
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list