I'm not 100% sure it's slon fault but since it's a beta release i'm posting.

I have node1 - master, node2 - slave, replication is working fine.
Upon testing the switchover scenario with the script:

        lock set (id = 1, origin = 1);
        wait for event (origin = 1, confirmed = 2);
        move set (id = 1, old origin = 1, new origin = 2);
        wait for event (origin = 1, confirmed = 2);
Both slon processes die and the switchover script idles
Starting slon on ex-node2 works fine and give the messages in attachment1.txt
Starting slon on ex-node1 dies with messages in attachment2.txt
Strace of slon on ex-node1 is in attachment3.txt <- notice the segfaults

http://dev.jokegurus.com/slony/attachment1.txt
http://dev.jokegurus.com/slony/attachment2.txt
http://dev.jokegurus.com/slony/attachment3.txt

-- 


Hi! I'm your friendly neighbourhood signature virus.
Copy me to your signature file and help me spread!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20050420/2b785b44/attachment.bin