Re: pg_dump bug fixing - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: pg_dump bug fixing
Date
Msg-id 1090298062.7056.13.camel@jester
Whole thread Raw
In response to Re: pg_dump bug fixing  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-hackers
On Mon, 2004-07-19 at 21:20, Christopher Kings-Lynne wrote:
> > We already are to some extent, since pg_dump will dump its comment and
> > privileges, which it would not do for any other predefined object.
> > I think this is actually an implementation artifact rather than
> > something that was explicitly intended at the time, but since no one
> > has complained about it, it's probably a good thing ;-)
> 
> Does that mean your in favour of dumping a DROP SCHEMA public; command 
> if they have dropped their public schema?  It's definitely not worth 
> doing it for any other "system" object due to upwards compatibility of 
> the dump files...

Please don't. It would be rather surprising to have stuff disappear from
a database while doing a restore -- especially if it's a CASCADE
operation.

Creating the public schema when needed and leaving it out by default is
preferable.




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PITR COPY Failure (was Point in Time Recovery)
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_config