Mon Jun 30 06:08:38 PDT 2014
- Previous message: [Slony1-commit] Slony-I-commit updates/fixes to the failover unit tests
- Next message: [Slony1-commit] Slony-I-commit fixing generate load origin node parameter mismatch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bug 342 - Fix various failover issues This commit fixes some related failover issues 1. The query slonik used to get a node list during failover was ignoring non-failover targets. This meant that we would never call preFailover on a node that wasn't a failover target. This node might then still be trying to use a failed provider. 2. A node (say node 3) might process a FAILOVER_NODE event from node 2 (the new-origin) but might not have yet processed the last event from node 1, the failed node. We need to make sure that the subscription paths and listen networks are updated so we don't only listen for events and data from failed nodes. Branch ------ REL_2_2_STABLE Details ------- http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=e1f05831c7418d4ca8e92ab16e8c6fba9938fbd2 Modified Files -------------- src/backend/slony1_funcs.sql | 52 ++++++++++++++++++++++++++++++++++-------- src/slonik/slonik.c | 44 ++++++++++++++++++++++++++--------- 2 files changed, 75 insertions(+), 21 deletions(-)
- Previous message: [Slony1-commit] Slony-I-commit updates/fixes to the failover unit tests
- Next message: [Slony1-commit] Slony-I-commit fixing generate load origin node parameter mismatch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list