Thanks Vivek.

I saw your post before and did try your suggestion.

Going through the list file was a nightmare since the replication stuff 
is littered all over the place, and its not always obvious (to me) what 
are slony versus non slony objects. We have lots of replicated tables 
and sequences and the listing file is quite long.

Much simpler to do a full load, and then somehow uninstall the 
replcation schema and triggers. Just two or three discrete operations - 
less for me to screw up!

Just gotta figure out how to do it.

John Sidney-Woollett

Vivek Khera wrote:

> 
> On Feb 9, 2005, at 10:13 AM, John Sidney-Woollett wrote:
> 
>> Here's what we're attempting (to build the test database):
>>
>> # DUMP FULL DATABASE
>> /usr/local/pgsql/bin/pg_dump $SRC_DATABASE > $BACKUPFILE
>>
>> # IMPORT THE DUMP FILE
>> psql $DEST_DATABASE < $BACKUPFILE
>>
> 
> I just did a restore for running some analysis on another local system. 
>  Basically the process was
> 
> pg_dump -Fc dbname
> pg_restore -l dumpfile > list
> edit list to remove all slony-related objects (tables, triggers, 
> functions, etc.)
> pg_restore -L list  dumpfile
> 
> this restored a cleaned copy.  this works for me since all my tables 
> aready had primary keys and slony didn't need to add columns to them.
> 
> Vivek Khera, Ph.D.
> +1-301-869-4449 x806
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general