During a switchover test, we got the following error message:

ERROR:  Slony-I: Node is uninitialized

It happened because a table we were using for a heartbeat monitor
erroneously had an extra slony trigger in place for a different (no
longer active) slony cluster.  

Totally strange circumstance, and totally my fault, but debug time would
have been much reduced if the error message had told us which node in
which cluster was not initialised.

Is there any chance that this information could be added to the error
message in a future release?

Thanks.

__
Marc Munro
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20051007/ead6f71d/attachment.bin