<p>Right, Steve mentioned as much on #slony earlier. My understanding from his and your comment, and the documentation, is that I'll need to follow the sequence below:</p>
<p>1. Create a new, empty set<br>
2. Subscribe all old nodes to the new set<br>
3. Do 'set move table' and 'set move sequence' for the tables and sequences to split out<br>
4. Finally, subscribe the new node to only this new set</p>
<p>Will that do what I want, without disturbing the already-loaded tables on the old nodes? <br>
</p>
<div class="gmail_quote">Den 8 apr 2012 02:35 skrev "Vick Khera" <<a href="mailto:vivek@khera.org" target="_blank">vivek@khera.org</a>>:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thu, Apr 5, 2012 at 5:47 AM, Johan Wärlander <<a href="mailto:johan@snowflake.nu" target="_blank">johan@snowflake.nu</a>> wrote:<br>
> Do I just add a new set with these particular tables, even though they<br>
> already exist in set1? Will this add a lot of traffic, or simply reuse the<br>
> existing logs?<br>
<br>
The sets need to be non-intersecting.<br>
_______________________________________________<br>
Slony1-general mailing list<br>
<a href="mailto:Slony1-general@lists.slony.info" target="_blank">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>
</blockquote></div>