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

Le 07/04/2010 03:42, Ben Chobot a écrit :
> On Apr 6, 2010, at 5:03 PM, Ben Chobot wrote:
> 
>> In our maintenance today we managed to confuse slony 1.2.20 by adding and dropping nodes. Now, sl_status shows nodes we have deleted, while sl_node correctly shows those nodes as gone.
>>
>> Any advice on how to clean up slony's config? The nodes in sl_node seem to be replicating correctly.... it's just a matter of removing all references to the deleted ones.
> 
> Actually, it seems that after an hour or so slony is no longer confused, which leaves me confused. :(
> 
> Why might slony be in such an apparently (but not really?) inconsistent state?

Hi,

In fact, Slony did not get confused. sl_status is a view composed with
information from sl_event and sl_confirm.
Until every event referencing the deleted nodes disappear from these tables,
you will see these nodes in sl_status.

The fact that these nodes are not shown in sl_nodes is a good way to know they
don't exist in the cluster anymore.

Best regards,
- --
Stéphane Schildknecht
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAku8OgoACgkQA+REPKWGI0GlpwCfUiqkZwN5XdpePfAhcUEADwMe
1swAoMuOoxZGp0G4KgtLsxt54rvXegQZ
=F7D6
-----END PGP SIGNATURE-----