Thu Dec 9 13:02:57 PST 2010
- Previous message: [Slony1-bugs] [Bug 174] Isolated Nodes
- Next message: [Slony1-bugs] [Bug 174] Isolated Nodes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=174 --- Comment #5 from Steve Singer <ssinger at ca.afilias.info> 2010-12-09 13:02:58 PST --- (In reply to comment #2) > Proposed... Add a table that will be replicated via event publishing that > captures tuples of the form [excluder, excludee] > > That is, node [excluder] will ignore events coming from node [excludee]. > > (Open question: Will it just be SYNC events that are ignored? Seems quite > likely apropos...) How would WAIT FOR (todays manual WAIT FOR - ignoring any automatic one) work if you ignore non sync events? Also, just because node 1 is excluding node 4 doesn't mean that node 3 is excluding node 4 (it probably isn't). How will WAIT FOR change. Also what are the implications with respect to FAILOVER and MOVE SET or rehshaping a subscription for this change. Also can you propose some syntax for making a node excluded? What happens if you no longer want a node to be excluded? Especially if the events have already been deleted on the excluder. -- 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.
- Previous message: [Slony1-bugs] [Bug 174] Isolated Nodes
- Next message: [Slony1-bugs] [Bug 174] Isolated Nodes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list