Re: pg_dump DROP commands and implicit search paths - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump DROP commands and implicit search paths
Date
Msg-id 21800.1021339460@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump DROP commands and implicit search paths  ("Rod Taylor" <rbt@zort.ca>)
List pgsql-hackers
"Rod Taylor" <rbt@zort.ca> writes:
> ... Based on the assumption a DROP SCHEMA statement will also
> be issued.

Doesn't seem very workable for the public schema.  I suspect pg_dump
has to special-case public anyway, to some extent, but this doesn't
really get us around the DROP problem for individual objects AFAICS.

I agree that if we issue a drop for the schema there's no need to
drop the individual objects ... but we aren't going to be issuing
any drops for public IMHO ... so we still need a solution that
supports dropping individual objects.

If we assume that schema retargeting is something that should be
done by a pg_restore option, then it'd probably be workable for
pg_restore to modify the qualified DROP commands as it issues them.
The main thing is to keep the explicit schema references out of the
CREATE commands, and that part I think is doable.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Rod Taylor"
Date:
Subject: Re: pg_dump DROP commands and implicit search paths
Next
From: Tatsuo Ishii
Date:
Subject: Re: [BUGS] Bug #659: lower()/upper() bug on