Re: pg_dump problems against 7.0 - Mailing list pgsql-patches

From Tom Lane
Subject Re: pg_dump problems against 7.0
Date
Msg-id 17180.1066697434@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump problems against 7.0  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: pg_dump problems against 7.0
List pgsql-patches
Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
>> Won't that result in *everything* being considered a system table?

> Doh.  Quite right.  Well, the 7.0 initdb creates pg_indexes as the last
> thing it does.  (Even though there are higher oids in pg_attribute,
> pg_rewrite and pg_description.), so how about the attached patch?

Seems reasonable, but the patch ought to fix the comment just above,
preferably with the above observation that this is correct by
examination of the now-frozen 7.0 initdb code ...

            regards, tom lane

pgsql-patches by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: pg_dump problems against 7.0
Next
From: Gaetano Mendola
Date:
Subject: pg_autovacuum README patch