Message-ID: <50EDA034.80200@gmail.com>
Date: Wed, 09 Jan 2013 08:52:04 -0800
From: Adrian Klaver <adrian.klaver@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
	rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: emilu@encs.concordia.ca
CC: PostgreSQL SQL List <pgsql-sql@postgresql.org>
Subject: Re: How to generate drop cascade with pg_dump
References: <50EC9574.9060500@encs.concordia.ca>
In-Reply-To: <50EC9574.9060500@encs.concordia.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

On 01/08/2013 01:53 PM, Emi Lu wrote:
> Hello,
>
> May I know how to generate drop table cascade when pg_dump a schema please?
>
> E.g.,
> pg_dump -h db_server -E UTF8   -n schema_name  -U schema_owner --clean
> -d db_name >! ~/a.dmp
>
> In a.dmp, I'd like to get:
>
> drop table t1 cascade;
> drop table t2 cascade;
> ... ...
>
> Only dropping constraints within a schema is not good enough since there
> are dependencies on other schema.

That is a limitation of dumping by schema.

http://www.postgresql.org/docs/9.2/interactive/app-pgdump.html
"Note: When -n is specified, pg_dump makes no attempt to dump any other 
database objects that the selected schema(s) might depend upon. 
Therefore, there is no guarantee that the results of a specific-schema 
dump can be successfully restored by themselves into a clean database.

If you want to reach across schemas you either need to do a whole 
database dump or modify a partial dump or create your own script.

>
> Thanks a lot!
> Emi
>
>


-- 
Adrian Klaver
adrian.klaver@gmail.com


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql