Hi,

I add a set to an existing replication. I then added tables to that set, and
wanting to merge it with an existing one, I tried to subscribe each node to
that set.

Unfortunately, one of the node (72, see below) did not know about that set, and
subscription failed, leaving the whole replication in an unstable state.

I can't do anything as node 72 is trying to subscribe a unknown set.

I tried to switch 72 and 71, for the 2nd set. I succeeded, but then, node 71 is
unsuccessful at providing data for other nodes.

Trying to drop node 72 from replication with 1 as event node hangs. Presumably
due to a lock taken by node 1 for doing it.

So node 1 continue to try to access a node that does not exist, and 71 can't
provide data.

Do I have another option that rebuilding the wole replication ? That may be a
half day production break at least...

More information:
PG 8.2.6
Slony1-1.2.13
OS : Linux debian 2.6.18-6-amd64

My replication schema is composed of:
9 nodes
2 sets

The replication goes two ways :
Set 1 :
1--11--21
    \--23
    \--25
    \--26
    \--27
    \--71--72

Set 2 :
72--71--11--1
        \--23


Is there a known bug I wasn't aware of?
Did I make sthg wrong?
What sort of information could be useful?

Best regards,
-- 
Stéphane SCHILDKNECHT
Président de PostgreSQLFr
Tél. 09 53 69 97 12
http://www.postgresql.fr