Thu Sep 6 16:00:13 PDT 2007
- Previous message: [Slony1-general] failover doesn't remove triggers
- Next message: [Slony1-general] failover doesn't remove triggers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
What slonik script did you run. How did you run it. What was the output of slonik. On 9/6/07, Richard Yen <dba at richyen.com> wrote: > > sorry...1.2.9 > > --Richard > > > > On Sep 6, 2007, at 1:19 PM, Dmitry Koterov wrote: > > > Which Slony version do you use? > > > > On 9/6/07, Richard Yen <dba at richyen.com> wrote: Hi all, > > > > I had to execute a FAIL OVER command last night, and I looks like the > > command might be buggy? > > > > After executing the command, the subscribe table on the new master > > (node 2) had two rows, one signifying that it was the provider for > > node 3, the other had a blank provider column and had node 2 in the > > subscriber column. I'm supposing this is expected behavior? > > > > What really concerned me was that on the new master, the denyaccess > > triggers were still there, so my entire cluster was essentially read- > > only. Is there a way to remedy this? Or is there an explanation? > > > > --Richard > > _______________________________________________ > > Slony1-general mailing list > > Slony1-general at lists.slony.info > > http://lists.slony.info/mailman/listinfo/slony1-general > > > > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070906/= 7bcc9692/attachment.htm
- Previous message: [Slony1-general] failover doesn't remove triggers
- Next message: [Slony1-general] failover doesn't remove triggers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list