Thu Jan 27 08:19:26 PST 2011
- Previous message: [Slony1-bugs] [Bug 175] Monitoring cluster better
- Next message: [Slony1-bugs] [Bug 173] Slonik ABORT command
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=174 --- Comment #7 from Jan Wieck <janwieck at yahoo.com> 2011-01-27 08:19:26 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...) This definition is different from the original and changes the semantics fundamentally. The original idea is to "assume" confirmations in order to avoid keeping events and log data for distant remote nodes. That does not mean that we ignore events at all. It means that we don't care when a node 2 hops away catches up to them. -- 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 175] Monitoring cluster better
- Next message: [Slony1-bugs] [Bug 173] Slonik ABORT command
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list