Fri Sep 28 08:29:52 PDT 2012
- Previous message: [Slony1-general] Issue when adding node to replication
- Next message: [Slony1-general] Issue when adding node to replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12-09-28 11:23 AM, Jan Wieck wrote: > On 9/28/2012 9:15 AM, Steve Singer wrote: >> * we can't ignore SYNC events even though the dropped >> * node is not an origin it might have been an old >> * origin before a FAILOVER. Some behind node still >> * might need to get caught up from its provider. > > That assessment is actually wrong. Any data provider as well as the > origin will keep the data until all subscribers have confirmed it. > Simply changing the data provider of the behind node will be enough to > make it catch up from another provider. > But it can't get caught up if we execute/process a DROP NODE on the other provider first which is why the slonik_drop_node can't ignore non-sync events when computing the last event id to use for waiting. > > Jan >
- Previous message: [Slony1-general] Issue when adding node to replication
- Next message: [Slony1-general] Issue when adding node to replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list