Tue Apr 12 13:22:09 PDT 2011
- Previous message: [Slony1-commit] Slony-I-commit Add sl_event_lock table that is what gets locked to prev
- Next message: [Slony1-commit] Slony-I-commit Add guard (via locking sl_event_lock) to ESTABLISH_SUBSC
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bug #196 - snapshot id values appear to travel backwards in sl_event Put in a lock on a new table, event_lock, whenever events are trying to generate a SYNC event, and make sure this is the very first thing executed, to prevent anything else from race-conditioning in to get the SYNC first Merge remote-tracking branch 'github/bug196' Conflicts: RELEASE src/backend/slony1_funcs.sql Branch ------ master Details ------- http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=15438c027374e9eed5f74219d3a1877c621fbde2 Modified Files --------------
- Previous message: [Slony1-commit] Slony-I-commit Add sl_event_lock table that is what gets locked to prev
- Next message: [Slony1-commit] Slony-I-commit Add guard (via locking sl_event_lock) to ESTABLISH_SUBSC
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list