Tue Mar 1 12:14:16 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 #2 from Steve Singer <ssinger at ca.afilias.info> 2011-03-01 12:14:16 PST --- (In reply to comment #1) > Preliminary implementation... > > https://github.com/cbbrowne/slony1-engine/tree/bug196 > > -------------------------------------------------------------------------------- > Add sl_event_lock table that is what gets locked to prevent mis-serialization > of creation of sl_event entries. > > Add pre_event_create() function that takes out that lock which will be called > by anything that does an event create. I think that function needs to be a C function not a stored procedure. The act of calling the stored procedure creates a snapshot - when the SELECT starts. THe lock doesn't get created until the 'LOCK statement' inside the stored procedure runs. -- 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