Fri Aug 27 11:30:28 PDT 2010
- Previous message: [Slony1-commit] Slony-I-commit Updating release notes for Bugs 132, 139 and 136.
- Next message: [Slony1-commit] Slony-I-commit Replace usage of alarm() for restarting slon with a KILL
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Commit: http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=d50fba024aac79020549973e98a4ea9d5bccdab5 Log Message ----------- When doing a fail node where the failed node is not a provider of the backup node we need to delete any subscribe entries that are used to forward data to the backup node. These will not be needed when the backup node becomes the new origin. Until that happens they get in the way of the FAILOVER_SET message that will be posted on the 'most ahead node' but iwth an origin of the old origin from getting to this node. Branch ------ REL_2_0_STABLE Modified Files -------------- src/backend/slony1_funcs.sql | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-)
- Previous message: [Slony1-commit] Slony-I-commit Updating release notes for Bugs 132, 139 and 136.
- Next message: [Slony1-commit] Slony-I-commit Replace usage of alarm() for restarting slon with a KILL
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list