> On 12/6/2004 8:23 PM, James Black wrote:
>> Hello, all,

>> merge set (id = 1, add id = 999, origin = 1);
>
> not only is it kosher, but the only way it works. The two sets you want
> to merge must have the same origin and an identical list of subscribers.
> Due to some sillyness in the way "subscribe set" currently works
> internally, you unfortunately cannot issue any "wait for event" to have
> the slonik script waiting until all the subscribers have finished
> copying the initial data for the new tables. So you will have to put the
> "merge set" part into a separate script run later.

Has anyone else noticed that if he forgets to run "merge set" later, there
will be noticably reduced performance until he does ?

In other words, replicating the same tables using multiple sets is
slower/harder for slony than replicating them using one set.

If it is a known problem, can anybody explain, why it must be so ?

Coult the reason be that cleanup thread fails to truncate sl_log_1 in
this case ?

-----------
Hannu