Re: pg_dump problems against 7.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: pg_dump problems against 7.0
Date: 2003-10-21 00:50:34
Message-ID: 17180.1066697434@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)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

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Gaetano Mendola 2003-10-21 00:54:18 pg_autovacuum README patch
Previous Message Christopher Kings-Lynne 2003-10-21 00:47:29 Re: pg_dump problems against 7.0