Fri Jun 4 09:52:07 PDT 2010
- Previous message: [Slony1-bugs] [Bug 129] FAILOVER command does not update sl_subscriber
- Next message: [Slony1-bugs] [Bug 134] New: TRUNCATE support
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=129 --- Comment #4 from Steve Singer <ssinger at ca.afilias.info> 2010-06-04 09:52:07 PDT --- The previous comment should have read: There is a second problem in the scenario described above. Node 3 has two subscribers (4 and 5) for the set. Since it has more than one direct subscriber failedNode() doesn't switch the subscriptions but expects slonik to do it. Slonik in slonik_failed_node() determines num_sets by this query select S.set_id, count(S.set)id) from sl_set S, sl_subscribe SUB where S.set_id = SUB.sub_set " and S.set_origin = 3 and SUB.sub_provider =3 and SUB.sub_active " group by set_id The problem is that node 3 is NOT the origin for set 1 it is just a forwarding provider so the query comes back with nothing. This means that later on in the function we don't loop over any replication sets (so we never call subscribeSet(...) or failedNode2(...) -- 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] FAILOVER command does not update sl_subscriber
- Next message: [Slony1-bugs] [Bug 134] New: TRUNCATE support
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list