Hi all.
My name is Juanky Moral. I've read all the documents (at Gborg,
General Bits articles, ...) , and many posts to slony-general as
possible, but I still need your help:

I build and installed slony1-1.0.5 to try replicate a small database
(11 tables, 5 sequences).
All the tables are keyed_tables.
I've configured a simple cluster: one master - one slave.
All things seem to work fine, but when I try to do any update on
master (using psql) for testing purposes, psql client aborts and local
slon process die.
This is what I see in the log.out:

CONFIG main: slon version 1.0.5 starting up
CONFIG main: local node id = 1
CONFIG main: loading current cluster configuration
CONFIG storeNode: no_id=2 no_comment='node2 en fernando'
CONFIG storePath: pa_server=2 pa_client=1 pa_conninfo="dbname=estafeta
host=fernando user=postgres" pa_connretry=10
CONFIG storeListen: li_origin=2 li_receiver=1 li_provider=2
CONFIG storeSet: set_id=1 set_origin=1 set_comment='tablas estafeta'
CONFIG main: configuration complete - starting threads
CONFIG enableNode: no_id=2
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back
the current transaction and exit, because another server process
exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and
repeat your command.
FATAL  syncThread: "start transaction;set transaction isolation level
serializable;select last_value from "_epvnet".sl_action_seq;" - server
closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.
WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back
the current transaction and exit, because another server process
exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and
repeat your command.
FATAL  localListenThread: cannot start transaction - server closed the
connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.
INFO   remoteListenThread_2: disconnecting from 'dbname=estafeta
host=fernando user=postgres'

Misteriously, the same cluster works well in other two nodes (fernando
-> isabel).
All nodes run PostgreSQL 8.0 (compiled) and Debian GNU/Linux.

Thanks in advance,

-- 
Juanky Moral
"Tendr? que moverme m?s r?pido: el horizonte brilla el?ctrico."
(Horizonte El?ctrico - www.losdeltonos.com )