Hello Slony Team,

Awesome work!. Have a quick question about a master node that is behind
a dynamic ip address dsl connection,

The master db replicates fine to the slave.
Master ip address changes, I'm thinking i can update the sl_path tables:

In master:
update _test2.sl_path set pa_conninfo='dbname=winls host=mmm.mmm.mmm.mmm
user=postgres' where _test2.sl_path.pa_server=1;

Then exact same command in slave:
update _test2.sl_path set pa_conninfo='dbname=winls host=mmm.mmm.mmm.mmm
user=postgres' where _test2.sl_path.pa_server=1;

and I restart the slon daemons in both master and slave with proper
host=mmm.mmm.mmm.mmm entry.

Slave slon seems to start ok
Master slon complains about:

CONFIG storeNode: no_id=2 no_comment='Node 2'
DEBUG2 setNodeLastEvent: no_id=2 event_seq=866
CONFIG storePath: pa_server=2 pa_client=1 pa_conninfo="dbname=mirror
host=sss.sss.sss.sss 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='WinLS tables'
DEBUG2 sched_wakeup_node(): no_id=1 (0 threads + worker signaled)
DEBUG2 main: last local event sequence = 911
CONFIG main: configuration complete - starting threads
DEBUG1 localListenThread: thread starts
FATAL  localListenThread: Another slon daemon is serving this node
already

I'm wondering if I need to do something else to change the connection
information in the master without re-initializing the entire cluster.
Most likely I'm missing something obvious.

Thanks for the help.

george