Chris Newland wrote:
> If it's a long way then is there any quick way to dump the application
> data from the master without all of the Slony information?

We take backups every hour of the master using pg_dump, and have 
successfully restored dumps to other servers (for test purposes for 
example). We don't take dumps from the slaves.

However the dump file from the master includes the slony replication 
schema. In order to  "get rid" of this schema, we use the following 
techniques which appear to work for us (with Slony 1.0.5). From my notes:

1) If the dump file loaded into the new database is a schema only dump, 
then create a specific uninstall script to connect to the new database 
and remove the slony replication info.

So after dumping you apply a single uninstall node statement on the new 
DB, eg

node 1 admin conninfo = 'dbname=XXXXXX host=YYYYY user=ZZZZZ';
uninstall node (id=1);

2) If the dump file is a full dump, load the dump file, then delete all 
records from _bpix_replcate.SL_TABLE and bpix_replcate.SL_SEQUENCE, then 
create and run a custom uninstall script as above.

Not sure that this a safe way to regenerate a db, but it appears to work 
OK. All Slony triggers appear to be removed correctly.

Hope that helps.

John Sidney-Woollett