On Wednesday 17 September 2008, Glyn Astill <glynastill at yahoo.co.uk> wrote:
> > It is well documented that you cannot use pg_dump to
> > retrieve the schema
> > of a subscriber. pg_dumpall uses pg_dump underneath to
> > create combined
> > schema+data dumps of all databases. This only works with
> > Slony 2.0.
>
> Thanks for clearing that up Jan.
>
> I was aware of that, however I discovered REPAIR CONFIG some time after
> I'd initially read that you couldn't restore pg_dump and that's obviously
> confused me to think that REPAIR CONFIG could work some sort of magic.

You can dump a subscriber node, but you have to take it offline and kludge 
the Slony stuff first (altertablerestore on all tables). And then repair 
the config after the restore (altertableforreplication and get the new 
table and sequence OIDs into the slony tables).

I've done it, and it's moderately faster than rebuilding replication on a 
new node, but it's a lot of stuff that has to be done right.

-- 
Alan