Darcy Buskermolen wrote:

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


Having another thought about that, using sl_rowid_seq to get unique ids 
seems sufficient. pgAdmin users will never need to enter an ID with that 
too.


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

That's right, but I'd suspect that in most cases it's sufficient 
assuming that the administrative interface of the node db server is the 
same for all admin clients (as opposed to inter-node traffic). I'm 
hesitating to invent another sl_path like configuration, which needs 
adjustment for every single client. At least, no_conninfo might serve as 
default value.

Regards,
Andreas