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

Jan Wieck <janwieck at yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|1.2                         |devel

--- Comment #2 from Jan Wieck <janwieck at yahoo.com> 2010-06-09 13:39:39 PDT ---
Changed version to devel because actually fixing this requires features.

UNSUBSCRIBE SET should continue to be issued against the subscriber. If the
event would originate from the set origin, the subscriber must crawl through
all the backlog to finally unsubscribe. That is a waste.

The processing of ENABLE_EVENT should on node -1 error simply confirm the
event, assuming that the subscription was canceled via UNSUBSCRIBE.

Upon receiving an UNSUBSCRIBE_SET event, the origin of that set will issue yet
another UNSUBSCRIBE_SET in order to guard against a possible race condition
where a third node, that is a forwarder for the set, receives the initial
UNSUBSCRIBE_SET before processing the initial SUBSCRIBE_SET. This would cause
it to wrongfully think that the node is actually subscribed to the set.


Jan

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