Fri Aug 27 11:30:13 PDT 2010
- Previous message: [Slony1-commit] Slony-I-commit If the nodelock can not be obtained then the worker will
- Next message: [Slony1-commit] Slony-I-commit Bug 136
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Commit: http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=bfa8e601fe7ba1bd91a053901426d4f7195c53a0 Log Message ----------- If a origin node fails a subscriber might not be listening for events from the new origin. The FAILOVER event gets processed on the subscriber but nothing after might be since the sl_listen rows are setup so all events from the new origin get routed through the node that used to be the provider(even if a direct path from the new origin to the subscriber exists). On processing the FAILOVER event we will mark the old origin as no inactive. RebuildListenEntries will now not remove paths that are dedundent if the (otherwise) preferred path flows through a disabled node. (cherry picked from commit 60566590d683b85733404ef290e6c1823c4c014c) Branch ------ master Modified Files -------------- src/backend/slony1_funcs.sql | 11 +++++++++-- 1 files changed, 9 insertions(+), 2 deletions(-)
- Previous message: [Slony1-commit] Slony-I-commit If the nodelock can not be obtained then the worker will
- Next message: [Slony1-commit] Slony-I-commit Bug 136
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list