> 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...