I just ran "slonik_uninstall_nodes" and got an error about a missing
table. After I thought I fixed it, I got this response when I ran it again:

root at sap# slonik_uninstall_nodes | slonik
<stdin>:4: PGRES_FATAL_ERROR select "_ff".uninstallNode();  - ERROR:
schema "_foo" does not exist

What happened was the table error was on node 1, which is uninstalled
/after/ node2. I think node 2 was successfully uninstalled on the first
try.

So when I re-ran the script, I think it's bombing out because node2 no
longer exists.

It would be more clearer and helpful if the feedback looked like this
instead:

 Node 2 appears to already be uninstalled. Skipping.
 Node 1:<stdin>:4: ... (node 1 errors, if any, here).

Now I've gotten myself into a pickle, because during the time I thought
node 1 was somehow half-uninstalled, I manually deleted the triggers
myself, and now the normal "uninstall" technique no longer works...so
I'll have figure how the rest of how to manually de-install slony on
this node, I suppose.

  Mark