Fri Aug 27 11:30:13 PDT 2010
- Previous message: [Slony1-commit] Slony-I-commit Add release notes for bug #124
- Next message: [Slony1-commit] Slony-I-commit If a origin node fails a subscriber might
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Commit: http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=283bb050e9efb84fcd90151c2432fd1eed4826b1 Log Message ----------- If the nodelock can not be obtained then the worker will keep retrying instead of exiting. Bug # 132 discussses issues where slon can't restart because of a duplicate node lock. The watchdog instance of slon can kill the worker child and restart it. The issue is that postgresql backend for the old worker might still be around when the new worker tries to get the nodelock. Prior to this patch we only had one shot at this, now we will keep retrying until a user decides to kill this process or the other one goes away (cherry picked from commit acd46819bad1613764708b138ebcfa895467ac51) Branch ------ master Modified Files -------------- src/slon/local_listen.c | 34 +++++++++++++++++++++------------- 1 files changed, 21 insertions(+), 13 deletions(-)
- Previous message: [Slony1-commit] Slony-I-commit Add release notes for bug #124
- Next message: [Slony1-commit] Slony-I-commit If a origin node fails a subscriber might
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list