On February 10, 2005 05:24 am, Andreas Pflug wrote:
> 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.

I'll look into this one further and see if the current logic is still prudent.

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

No dis-agreement here.

>
> - 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.

Jan/Chris thought on this one ?
>
> - 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).

The problem with this is that path may change depending on where you are 
admining from.


>
> Regards,
> Andreas
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general

-- 
Darcy Buskermolen
Wavefire Technologies Corp.
ph: 250.717.0200
fx:  250.763.1759
http://www.wavefire.com