<div dir="ltr">Thanks Steve for your suggestion. <div><br></div><div>The issue stays resolved.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 22, 2014 at 9:10 PM, Steve Singer <span dir="ltr"><<a href="mailto:steve@ssinger.info" target="_blank">steve@ssinger.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Fri, 22 Aug 2014, Venkata Balaji N wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello Everyone,<br>
We have a situation where Slony schema on a slave node was accidentally dropped.<br>
<br>
Is there any quick way around for this ?<br>
<br>
We have a master replicating to 3 slaves and one of the slaves does not have the Slony schema.<br>
<br>
- Can we just un-subscribe that slave and resubscribe back to catch up with the sync ?<br>
<br>
In anyone faced such situation, please help us with this.<br>
</blockquote>
<br></div></div>
You should issue a DROP NODE command for the slave that lost the schema (using another node as the event node).<br>
<br>
You can then create the node again as a new node and resubscribe.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Regards,<br>
VBN<br>
<br>
<br>
</blockquote>
</blockquote></div><br></div>