Wed Jun 23 06:51:57 PDT 2010
- Previous message: [Slony1-bugs] [Bug 130] failover does not seem to update sl_set
- Next message: [Slony1-bugs] [Bug 56] store trigger runs against all nodes upon subscription
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=129 Steve Singer <ssinger at ca.afilias.info> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.slony.info/bugz | |illa/show_bug.cgi?id=130 Resolution| |DUPLICATE Status|NEW |RESOLVED --- Comment #7 from Steve Singer <ssinger at ca.afilias.info> 2010-06-23 06:51:57 PDT --- I am marking this bug as a duplicate. The two issues raised below are better described by bugs 130 and 136. 130: should address the case of sl_subscriber not showing the new information when the FAILOVER finishes failing node 1==>3, we need waits 136: Deals with the case of 3===>1 where 3 is just a provider/forwarder, we don't want to use the FAILOVER command in this case, we just want the SUBSCRIBE to always work. *** This bug has been marked as a duplicate of bug 136 *** -- 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.
- Previous message: [Slony1-bugs] [Bug 130] failover does not seem to update sl_set
- Next message: [Slony1-bugs] [Bug 56] store trigger runs against all nodes upon subscription
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list