Fri Feb 1 11:16:20 PST 2013
- Previous message: [Slony1-commit] Slony-I-commit Bug 285 fix move set race condition.
- Next message: [Slony1-commit] Slony-I-commit updating to release 2.2.0 B3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bug 285 fix move set race condition. During a move set it is possible on subscriber node, that isn't the old or new origin, for remoteWorkerThread_$oldorigin to start processing a SYNC event before the ACCEPT_SET is processed by the remoteWorkerThread_$neworigin. If the ACCEPT_SET transaction then commits before the update sl_setsync query is executed by the remoteWorkertThread_$oldorigin the update will update a row for the new origin when it intends to update the old origin. This messes up sl_setsync. This change will add a condition to the WHERE clause so a remoteWorkerThread won't UPDATE rows for a different origin Branch ------ master Details ------- http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=3db179500c3144cd311edd5b512818f949506c57 Modified Files -------------- RELEASE | 2 ++ src/slon/remote_worker.c | 5 ++--- 2 files changed, 4 insertions(+), 3 deletions(-)
- Previous message: [Slony1-commit] Slony-I-commit Bug 285 fix move set race condition.
- Next message: [Slony1-commit] Slony-I-commit updating to release 2.2.0 B3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list