Fri Oct 20 09:29:59 PDT 2006
- Previous message: [Slony1-general] slony 1.1.5 woes
- Next message: [Slony1-general] Slony-I 1.2.0 Available
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 10/20/06, Andreas Kostyrka <andreas at kostyrka.org> wrote: > > Aha. It wasn't clear to me, from your original mail, that you'd > > changed things quickly. But yes, this could be the problem. In my > > experience, you need to ensure you have some WAIT FOR EVENT > > What nodes should I wait after changing the provider for a given > receiver? > > You need to tell the new origin to wait for the lock set event. The admin guide suggests the following: lock set (id = 1, origin = 1); wait for event (origin = 1, confirmed = 2); move set (id = 1, old origin = 1, new origin = 2); wait for event (origin = 1, confirmed = 2); (See http://linuxfinances.info/info/failover.html) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://gborg.postgresql.org/pipermail/slony1-general/attachments/20061020/a8f80222/attachment.html
- Previous message: [Slony1-general] slony 1.1.5 woes
- Next message: [Slony1-general] Slony-I 1.2.0 Available
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list