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.


Also, sl_log_2 is up to 1M rows and I see that slony FETCH queries are
slow. Could this down node be causing the large numbers of log entries?

I'm using slony version Using 1 2.0.1.

Thanks.