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

           Summary: Isolated Nodes
           Product: Slony-I
           Version: devel
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: low
         Component: slonik
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: cbbrowne at ca.afilias.info
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


Per [http://lists.slony.info/pipermail/slony1-general/2010-November/011353.html
discussion on list]

* Allow configuring that some nodes should be ignored for the purpose
  of confirmations.

* This allows the cleanup thread to trim out sl_log_(1|2) data for the
  ignored nodes

* FAILOVER may already support the notion that an "ignored" node might
  be lost.

* An interesting extension: SUBSCRIBE SET might automatically mark the
  "child" node as shunned until such time as the subscription has
  completed and caught up.  This only works if only one set is
  involved; if there are multiple subscriptions, shunning only works
  out well for the first one.

* [Jan] It will work just fine for multiple subscriptions. The point
  here is to free the master and other forwarders than the data
  provider for the node, that is busy subscribing, from keeping copies
  of the log.

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