<p dir="ltr">I guess you mean either UNSUBSCRIBE SET or DROP NODE.</p>
<p dir="ltr">What should happen in the UNSUBSCRIBE case is that the node quickly confirms all the outstanding events since they no longer require replicating any data, at which point all providers can perform/finish log switching again. </p>
<p dir="ltr">In the case of DROP NODE the behavior is similar. Make sure that ALL remaining nodes in the cluster have forgotten everything about the dropped node before attempting to rebuild it. Or rebuild it with a different node ID.</p>
<p dir="ltr">If this is your only node, then you could as well uninstall the whole cluster and start from scratch.<br><br><br></p>
<p dir="ltr">--<br>
Jan Wieck<br>
Senior Software Engineer<br>
<a href="http://slony.info">http://slony.info</a></p>
<div class="gmail_quote">On Jun 27, 2014 4:04 PM, "Dave Cramer" <<a href="mailto:davecramer@gmail.com">davecramer@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">If I drop the subscription through drop set will the log file be automagically cleaned up ?<div><br></div><div>If not how can I fix it ?</div><div><br clear="all"><div>Dave Cramer</div>
</div></div>
<br>_______________________________________________<br>
Slony1-general mailing list<br>
<a href="mailto:Slony1-general@lists.slony.info">Slony1-general@lists.slony.info</a><br>
<a href="http://lists.slony.info/mailman/listinfo/slony1-general" target="_blank">http://lists.slony.info/mailman/listinfo/slony1-general</a><br>
<br></blockquote></div>