I'm currently implementing Slony-I support in pgAdmin3, and found some
issues which I'd propose to change.

- Apparently, there are no version differences in the scripts to execute
when creating a replication cluster. It would make life easier if the
scripts would be reduced to slony1_base, slony1_funcs and slony1_xxid.

- To save OIDs I'd propose to define the tables WITHOUT OIDS

- sl_table and sl_sequence replication to client nodes is deferred until
a subscription is started. IMHO both should be replicated immediately
(just as sl_set), because their tab_id/seq_id must be unique across the
cluster and in case of complicated scenarios it might well happen that a
duplicate id is used which is not discovered until the subscription is
started.

- It would be quite handy if sl_node would be extended by a column
no_conninfo which contains a connect string, effectively a path for
external tools (equivalent to ADMIN CONNINFO).

Regards,
Andreas