Fri Jul 26 07:44:15 PDT 2013
- Previous message: [Slony1-commit] Slony-I-commit Lots of fixes to anachronisms in FAQ
- Next message: [Slony1-commit] Slony-I-commit don't process a set if sl_setsync has the initial :1:1:
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
bug 299 - put the WAKEUP event at the front of the event queue instead of the back. This will prevent the remoteWorker thread for an old-origin from pulling the set that was just moved if a SYNC event is already queued Branch ------ master Details ------- http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=938d6cbc5fbb7d40b55bf0a8336a6a1006ffcfc5 Modified Files -------------- src/slon/remote_worker.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
- Previous message: [Slony1-commit] Slony-I-commit Lots of fixes to anachronisms in FAQ
- Next message: [Slony1-commit] Slony-I-commit don't process a set if sl_setsync has the initial :1:1:
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list