Karl Denninger <karl at denninger.net> writes:
> I have been dorking around with setting up replication and while I
> seem to be able to remove sets and such, I have been unable to drop an
> entire cluster.
>
> Can that be done?

That needs to be done by uninstalling Slony-I on each node.

The relevant Slonik command is UNINSTALL NODE:
   <http://www.slony.info/adminguide/slony1-1.2.6/doc/adminguide/stmtuninstallnode.html>

If you have 5 nodes, you'd need to run UNINSTALL NODE against each
one.

> Also, what tables do I query to see what slony has configured in it
> in a "total view" perspective?

I'm not quite sure what you mean by "total view perspective."

Each of the tables in the Slony-I schema contains some aspect of "what
is configured" *except* for those that contain history/logging
information.

 - sl_node contains the list of nodes
 - sl_table contains the list of replicated tables
 - sl_sequence contains the list of replicated sequences
 - sl_path contains configuration surrounding how slon processes
   communicate with other nodes

Those are the "heavy hitters" as far as the grand scheme of
configuration is concerned; the other tables tend to contain somewhat
less interesting information (that is nonetheless necessary :-)).
-- 
output = reverse("ofni.secnanifxunil" "@" "enworbbc")
http://cbbrowne.com/info/internet.html
Rules of  the Evil Overlord  #136. "If I  build a bomb, I  will simply
remember which wire to cut if  it has to be deactivated and make every
wire red." <http://www.eviloverlord.com/>