On 6/29/07, Filip Rembia=B3kowski <plk.zuber at gmail.com> wrote:
>
> 2007/6/29, Raymond O'Donnell <rod at iol.ie>:
> > On 28/06/2007 23:17, Christopher Browne wrote:
> >
> > > There's a further "wish list" we're looking at, for which it seems
> > > timely to solicit additions:
> >
> > Maybe I'm missing something blindingly obvious (I'm pretty inexperienced
> > with Slony), but would it be possible to produce a tool that allows a
> > dump of a replicated node *without* all the extra stuff Slony adds - the
> > extra schema, triggers, etc. - in other words, output similar to that
> > produced by pg_dump on an unreplicated database?
>
> Good point IMHO; similar need here. I guess many people need this.
>
> To produce a "clean" dump ( that is, without Slony-I schema and
> triggers ) we have to install temporary backup node, wait for it to
> catch up, DROP NODE it , and dump it.  Whole process takes almost
> twice longer as plain pg_dump (and is more failure-prone)
>
>
>
I think the developers have it on the "TODO" list:

----------------

Differences from 1.2 stream

- Removal of TABLE ADD KEY

- It drops all support for databases prior to Postgres version 8.3.

This is required because we now make use of new functionality in
Postgres, namely the trigger and rule support for session replication
role. As of now, every node (origin/subscriber/mixed) can be dumped with
pg_dump and result in a consistent snapshot of the database.

----------------

Regards

MP
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070629/=
9c691aa2/attachment.htm