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

David Parker wrote:

| Given these two databases that have been broken apart by a FAILOVER,
| is there any way to get the old master re-subscribed without
| loosing all of the data?

No, not currently. There's probably little call for this since the
semantics of FAILOVER involve accepting data-loss on the old origin.
This implies that data on the old origin and the new origin may be
different.

Healing from a FAILOVER is a very complicated thing to do. I've seen
some interesting literature exploring this area in the CS journals
(typically in the context of distributed filesystems), but nobody's
seriously attempted to implement it for a production system yet, as far
as I know.

| Assuming there is no existing slonik functionality for this,
| is there some combination of sl_* table fiddling and slon re-sync
| that I could implement to make slony accept the old master as a
| new subscriber without going through the subscribe initial truncation?

Probably, but I'd strongly recommend that you don't do this (foot-cannon
would be an understatement). The approach that I'd suggest is to
investigate the Hendrik "cold-add" patch.

- --
Andrew Hammond    416-673-4138    ahammond at ca.afilias.info
Database Administrator, Afilias Canada Corp.
CB83 2838 4B67 D40F D086 3568 81FC E7E5 27AF 4A9A
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBgl3Ugfzn5SevSpoRAnkjAJ9ZM/Y7za+xb5lkAm6GAhFS6mkwhQCfSP+y
76NwSidHV0SS6wRkI4hc7rA=
=5ww6
-----END PGP SIGNATURE-----