Gurjeet Singh wrote:

> The doc-patch does make it more clear, but I don't think DROP SCHEMA 
> _slony_cluster_name CASCADE is something I'd like to do with my running 
> Slony replication. A cleaner way would be more desirable.

Another option you have is to restore the dump that you create of your 
pgbench schema to another database(a new one).  When you restore the 
CREATE TRIGGER statements will fail because the slony stored procedures 
won't exist in your new database.   This should leave you with your 
database - any slony stuff.  (I agree having to put up with 'errors' 
during the restore or make a second copy of the database just to do 
'DROP SCHEMA' are both less than ideal solutions)




> 
> Regards,
> -- 
> gurjeet.singh
> @ EnterpriseDB - The Enterprise Postgres Company
> http://www.enterprisedb.com
> 
> singh.gurjeet@{ gmail | yahoo }.com
> Twitter/Skype: singh_gurjeet
> 
> Mail sent from my BlackLaptop device


-- 
Steve Singer
Afilias Canada
Data Services Developer
416-673-1142