Tue Apr 12 13:22:09 PDT 2011
- Previous message: [Slony1-commit] Slony-I-commit There a few more places to adjust, as there are stored f
- Next message: [Slony1-commit] Slony-I-commit Add sl_event_lock table that is what gets locked to prev
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
No value in having pre_event_create() function... That leaves the race condition in place. We need to submit the LOCK TABLE request *immediately* after the BEGIN, with *NO* database logic intervening at all Branch ------ master Details ------- http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=adcdc8cc167ec8d8b37009039c89e28ea6fcc788 Modified Files -------------- src/backend/slony1_funcs.sql | 10 ---------- 1 files changed, 0 insertions(+), 10 deletions(-)
- Previous message: [Slony1-commit] Slony-I-commit There a few more places to adjust, as there are stored f
- Next message: [Slony1-commit] Slony-I-commit Add sl_event_lock table that is what gets locked to prev
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list