Tue Feb 16 14:55:28 PST 2010
- Previous message: [Slony1-general] drop node not working correctly
- Next message: [Slony1-general] drop node not working correctly
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Feb 16, 2010 at 4:30 PM, Christopher Browne <cbbrowne at ca.afilias.info> wrote: > Perhaps > configuration should be pretty much synchronous, checking state against > all the nodes, and griping if *any* of them disagree. If this were the case, you could only ever run configuration changes when replication had essentially zero lag. Ie, all nodes are up to date. If you did, you'd end up waiting until all the events were propagated, possibly with locks being held.
- Previous message: [Slony1-general] drop node not working correctly
- Next message: [Slony1-general] drop node not working correctly
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list