Wed May 26 14:26:43 PDT 2010
- Previous message: [Slony1-bugs] [Bug 129] New: FAILOVER command does not update sl_subscriber
- Next message: [Slony1-bugs] [Bug 131] New: two concurrent subscribe sets can deadlock each other
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=130 Summary: failover does not seem to update sl_set Product: Slony-I Version: 2.0 Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: low Component: stored procedures AssignedTo: slony1-bugs at lists.slony.info ReportedBy: ssinger at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 Observed with 2.0.3 In a cluster as follows 1 \\ \\ 3===4 \\ \\ 5 A failover of set 1=>3 seems to work. However DROP NODE (id=1) fails with <stdin>:12: PGRES_FATAL_ERROR select "_disorder_replica".dropNode(1); - ERROR: Slony-I: Node 1 is still origin of one or more sets When I query sl_set it shows that node 1 is still the origin of the set even though the failover command seemed to work okay. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 129] New: FAILOVER command does not update sl_subscriber
- Next message: [Slony1-bugs] [Bug 131] New: two concurrent subscribe sets can deadlock each other
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list