Brett <brettelliott at gmail.com> writes:
> A machine housing a slony slave database went down and the machine is
> being worked on, meanwhile what is the best way to handle this? I'd like
> to for now delete the node in slony so I don't get errors such as:
>
> failed - could not connect to server: No route to host
>         Is the server running on host "10.2.1.30" and accepting
>         TCP/IP connections on port 5432?
>
> in the logs. SLONIK DROP NODE contacts the node to be dropped and issues
> commands on that node and obviously that won't work since the node is
> unavailable right now.

Actually, "obviously that won't work" isn't quite so...

You need to specify a different node as the EVENT NODE, and that
should work fine.
<http://www.slony.info/documentation/stmtdropnode.html>
-- 
"cbbrowne","@","ca.afilias.info"
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"