Re: pg_dump bug fixing - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump bug fixing
Date
Msg-id 22237.1090248271@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump bug fixing  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: pg_dump bug fixing  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-hackers
Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> I think that we should treat the public schema specially :)

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 ;-)

Also, if we're going to apply Fabien's proposed patch to alter the
ownership of the public schema, that's still another way in which the
public schema becomes less like a system-defined object ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: function return type
Next
From: Tom Lane
Date:
Subject: Re: Why we really need timelines *now* in PITR