http://www.slony.info/bugzilla/show_bug.cgi?id=296

--- Comment #3 from Steve Singer <ssinger at ca.afilias.info> 2013-06-27 13:49:23 PDT ---
Created an attachment (id=165)
 --> (http://www.slony.info/bugzilla/attachment.cgi?id=165)
proposed fixes for 296

I have pushed a set of fixes for these issues at
https://github.com/ssinger/slony1-engine/commits/bug296 or in the attached
patch.

This set of changes follows 1 and 2 from my previous comment but doesn't
exactly follow point 3.

We pass the complete list of failed nodes in the FAILOVER_NODE event, so in the
above example we would do
FAILOVER(node=(id=1, backup node=2), node=(id=3,backup node=5), node=(id=4,
backup node=2))

slonik will generate two FAILOVER_NODE events.  

FAILOVER_NODE (backup_node=2,failed_node=1,  seq_no=XXXXXXX,
failed_node_list=1,3,4])

FAILOVER_NODE (backup_node=5,failed_node=1,  seq_no=XXXXXXX,
failed_node_list=1,3,4])

Each node that proceses these events will know that the other two nodes have
also failed and to not repoint the sl_subscribe line for node 4 to a backup
node.

-- 
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.