Sat Aug 23 02:23:20 PDT 2014
- Previous message: [Slony1-general] Need help with a production issue
- Next message: [Slony1-general] Slony-I Upgrade
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thanks Steve for your suggestion. The issue stays resolved. On Fri, Aug 22, 2014 at 9:10 PM, Steve Singer <steve at ssinger.info> wrote: > On Fri, 22 Aug 2014, Venkata Balaji N wrote: > > Hello Everyone, >> We have a situation where Slony schema on a slave node was accidentally >> dropped. >> >> Is there any quick way around for this ? >> >> We have a master replicating to 3 slaves and one of the slaves does not >> have the Slony schema. >> >> - Can we just un-subscribe that slave and resubscribe back to catch up >> with the sync ? >> >> In anyone faced such situation, please help us with this. >> > > You should issue a DROP NODE command for the slave that lost the schema > (using another node as the event node). > > You can then create the node again as a new node and resubscribe. > > >> Regards, >> VBN >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20140823/85c5725e/attachment.htm
- Previous message: [Slony1-general] Need help with a production issue
- Next message: [Slony1-general] Slony-I Upgrade
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list