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

--- Comment #2 from Steve Singer <ssinger at ca.afilias.info> 2013-06-24 12:56:59 PDT ---
My proposal is that we should do the following

1. Require users to list all of the failed nodes on the FAILOVER command, even
non-origin nodes.

2. If a node isn't listed in the FAILOVER command as a failed node and if it is
a RECEIVER of a set from a failed node it MUST have a direct PATH to the backup
node.  We will check this early on and give an error.  Users can then do a
STORE PATH or add that node to the list of failed nodes.  

3. If a node is a non-origin and is listed as a failed node we redirect it to
the backup node by manipulating sl_subscribe and we post a FAILOVER event on
the backup node so all other nodes can update sl_subscribe as needed.  We avoid
issues
with foreign key violations between sl_subscribe -> sl_path and sl_listen ->
sl_path because the direct path exists.

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