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

--- Comment #2 from Steve Singer <ssinger at ca.afilias.info> 2010-06-23 06:47:11 PDT ---
According to the documentation DROP NODE shouldn't work with an EVENT_NODE=1
(the node being dropped) so I don't think that was the case.

I think what was happening is that FAILOVER returns right away but the failover
processing doesn't complete until later (the other subscribers have to process
an ACCEPT_SET).  No WAIT FOR commands where being issued after the FAILOVER.

See the comments on bug #129. relevant portion duplicated below

----------------
2) As part of a failover we want to mark the failed node as being inactive in
sl_node and make it so that WAIT FOR  confirmed=all don't wait on this failed
nodes to confirm things.

3) slonik needs to remember the sequence number returned by failedNode2 so that
it is possible to WAIT FOR that event on the backup node to ensure it is
confirmed by all.    Exactly how a slonik script can wait still needs to be
figured out.   This won't be done until 2.1
------------------------

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