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

--- Comment #2 from Steve Singer <ssinger at ca.afilias.info> 2010-07-27 11:55:26 PDT ---
I am worried that marking that we can't just ignore+mark confirmed the
subscribe set event on nodes where the set does not exist in sl_set.

node 5 would have no way of knowing if their is no row in sl_set because a DROP
SET has already been processed or if it is because the CREATE SET has not yet
been received by node 5.   Both the create set and the drop set will be coming
from the origin but the subscribe set could be coming from a receiver.

We could try to 'remmeber' the set after a DROP SET for some period of
time/messages but what would that period be? An arbitrary value would only
delay the issue.   You could remember all old sets, 

We could try to make the subscribe set come from the origin not from the
provider. This would mean that it comes from the same place as the create/drop
set commands but that will have implications elsewhere.

Ideas welcome

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