Alas, there is not presently a way to easily exclude all the Slony bits including triggers.
It is easy enough to exclude most Slony objects by using the -n option to leave off the appropriate schema. But the log triggers are tied to your tables, harder to exclude. You might integrate David's idea... Pg_dump with -n to exclude Slony objects Then grep to exclude (e.g. -v option) for logtrigger and denyaccess triggers. I'd hope that would be very close to loading cleanly. There have been ideas about extending pg_dump to allow fairly fine grained exclusion filters, akin to having sophisticated filters in 'find', but I think that's gotten deferred to Postgres 9.3. (Search pgsql-hackers for pg_dump, options, and I think Andrew Dunstan has been in on discussions if not initiator...)
_______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
