Wed Aug 4 11:05:21 PDT 2010
- Previous message: [PATCH 1/3] Replace usage of alarm() for restarting slon with a KILL of the child and a sleep before restarting.
- Next message: [PATCH 3/3] 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.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Steve Singer <ssinger at ca.afilias.info> writes: > Steve Singer wrote: > > This is a version of the bug118 patch for the 1.2 branch. > > Do we want to backport this bug to 1.2? > > (I'm thinking we do) Yep, I'd think so. -- let name="cbbrowne" and tld="ca.afilias.info" in String.concat "@" [name;tld];; Christopher Browne "Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock phasers on the Heffalump, Piglet, meet me in transporter room three"
- Previous message: [PATCH 1/3] Replace usage of alarm() for restarting slon with a KILL of the child and a sleep before restarting.
- Next message: [PATCH 3/3] 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.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-patches mailing list