-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Glyn Astill a écrit :
>> I know how to suppress everything in
>> sl_set/sl_table/sl_sequence. But I can
>> easily guess it won't be enough. So how could I be sure
>> I will delete all and
>> only information concerning set 3 in other tables (sl_event
>> may be the one I
>> should focus on, no ?) ?
> 
> Did you get anywhere with this Stephane?
> 
> Those are the four tables I'd be thinking to clean up, and it'd be interesting to know how you got on.
> 
> 
>       

Sorry, I wanted to inform you about the situation, and didn't get time. Now, I
do :-) Apologies for not having done it before.

I stopped slony daemons.
So, I deleted everything from sl_sequence, sl_set, sl_table on nodes where it
still had information about the third set (that is the 2 nodes that were not
synchronising anymore).
I then deleted every line in sl_event that was related to the set (lines
containing information on storing the set, dropping it or subscribing to it...
that was some 26 or 27 lines by node).
When all nodes were cleaned out from information regarding that set, I
restarted slony daemons, and restarted the create set/set add table and
sequences/subscribe set process.

And everything went fine.

Many thanks!

Best regards,
- --
Stéphane Schildknecht
PostgreSQLFr - http://www.postgresql.fr
Dalibo - http://www.dalibo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJQ4x6A+REPKWGI0ERArg/AKDNsW+HgxV3oS2DrMSl8l9+hMSW4wCgpzbu
ZCB2n1tqU6ELgFsepi4oITk=
=o7mA
-----END PGP SIGNATURE-----