Re: pg_dump bug fixing - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: pg_dump bug fixing
Date
Msg-id 40FC7363.2090905@familyhealth.com.au
Whole thread Raw
In response to Re: pg_dump bug fixing  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dump bug fixing  (Rod Taylor <pg@rbt.ca>)
List pgsql-hackers
> 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...

Chris



pgsql-hackers by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: PITR COPY Failure (was Point in Time Recovery)
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Point in Time Recovery