Re: Planned change in initdb-time OID allocation

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Planned change in initdb-time OID allocation
Date: 2001-08-07 02:51:10
Message-ID: 200108070251.f772pAE25923@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> What bothers me about this scheme is that genbki.sh can only create
> pg_description entries for objects with hand-assigned OIDs. It
> processes the DESCR() macro by emitting the OID of the last DATA macro,
> along with the description text, into a data file that's eventually
> copied into pg_description. But if there's no hand-assigned OID it has
> to punt --- it doesn't know what OID the object will have. This means
> we can't assign initdb-time descriptions to aggregate functions (for
> example), since we don't give them hand-assigned OIDs.

This was a known problem when I implemented pg_description. Your
solution sounds good.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-08-07 03:24:46 Re: Planned change in initdb-time OID allocation
Previous Message Mike Mascari 2001-08-07 02:50:55 Re: Planned change in initdb-time OID allocation