Re: pg_dump problems against 7.0

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: pg_dump problems against 7.0
Date: 2003-10-21 02:57:45
Message-ID: 200310210257.h9L2vj608535@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches


Is this supposed to be applied to CVS?

---------------------------------------------------------------------------

Christopher Kings-Lynne wrote:
> >>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 ...
>
> Attached.
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Christopher Kings-Lynne 2003-10-21 03:13:14 Re: pg_dump problems against 7.0
Previous Message Bruce Momjian 2003-10-21 02:49:52 Re: Make pg_dump dump conversions