Slony1 PostgreSQL Replication - change slave connection details

Author

change slave connection details

Victoria Parsons

2005-07-26, 9:24 am

Hi,

I want ot handle the case where a slave node may change its IP address. I will be informed by the slave so I don't have to detect it. I could do it bedropping the node completely, then readding with new conninfo, but that seems like overkill.

Can I do it just with stopping slon daemon for this node, use slonik DROP PATH, STORE PATH, and restarting slon daemon for this node?

____________________
____________________
__________

Victoria Parsons
Research & Development

StreamShield Networks

Tel 0870 114 9465
Fax 0870 114 9467

This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately.
Statements of intent shall only become binding when confirmed in hard copy by an authorized signatory.

--
This message has been scanned for viruses and potentially
harmful content by StreamShield Protector.

Christopher Browne

2005-07-26, 11:24 am

Victoria Parsons wrote:

> Hi,
>
> I want ot handle the case where a slave node may change its IP
> address. I will be informed by the slave so I don't have to detect it.
> I could do it be dropping the node completely, then readding with new
> conninfo, but that seems like overkill.
>
> Can I do it just with stopping slon daemon for this node, use slonik
> DROP PATH, STORE PATH, and restarting slon daemon for this node?
>
Dropping the node is overkill, to be sure.

You don't really even need to DROP PATH; you should just need to STORE
PATH with the new address.

You might need to restart slons for other nodes; I don't recall whether
things are smart enough for them to automagically drop and restart the
connection to the new IP. Mind you, since the old address they were
using has probably died, that might "glitch" things enough for them to
restart.

I'd be inclined to "cycle" the slons, myself...

Sponsored Links