hmm could be i've missunderstood something...

but it appears that move set does not change all the subscriptions to 
the orgin node?

It appear that if i got
1 -> 3
1 -> 2

and i do move set
from 1-> 3

1 will subscribe from 3, but 2 will continue to subscribe from 1.

how should I go about moving subscription on node 2 to point to 3 instead?

But I would think that changing the origin should change all the 
subscriptions but it appear not to do that.. from the manual:

"After this command, the set cannot be unlocked on the old origin any 
more. The old origin will continue as a forwarding subscriber of the set 
and the subscription chain from the old origin to the new origin will be 
reversed"

so that would just mean it just changes that specific provider <-> 
subscriber link not all of them?



Marcin Kasperski wrote:
>> if you try to issue "slonik_drop_node" on your previous master node
>> does it work?
>>     
>
> Yes, I already did it on the previous configuration.
>
>   
>> mine didn't as its claiming its still used, but maybe
>> its the same problem as you had and its just taking LONG to change the
>> subscription on my second slave...
>>     
>
> It went rather slow (a few mins on small database), but worked.
>
> Not sure whether this is related but earlier to move the node
> I had to kill some programs running on the same postgres instance
> (in spite of the fact that they worked on unrelated database)
>
> PS Maybe your database is not yet fully synchronized? Drop node
> will wait until earlier things are processed...
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>