On Thursday 21 September 2006 08:24, Andrew Sullivan wrote:
> On Thu, Sep 21, 2006 at 04:29:20PM +0300, Mikko Partio wrote:
> > an ideal candidate. The company I'm doing it doesn't really have
> > competent DBA's and therefore one of the requirements is to have an
> > "automatic replication" of a table.
> >
> > Perhaps one solution would be a script that periodically scans both
> > _clustername.sl_table and pg_tables and would look for tables that are
> > on the system table but not on the slony table. From there the script
> > would create a new set and add the table to that set (and perhaps merge
> > the new set with an old set). What do you think, would this be a
> > feasible solution?
>
> You could do it that way; but I'd prefer to see some tools that were
> Slony-aware database administration tools.  So, for instance, instead
> of using the psql CREATE TABLE interface, you disable psql for usual
> users, and give them a psql-sl that knows about slony.  It handles
> these automatic parts behind the scenes.  The obvious answer is some
> sort of gui that does it.

Gavin (swm) is working on an api to make the building of slony aware tools a 
whole lot easier.  I'm not sure on the current status of his work.
>
> A