Re: Planned change in initdb-time OID allocation - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Planned change in initdb-time OID allocation
Date
Msg-id 200108070251.f772pAE25923@candle.pha.pa.us
Whole thread Raw
In response to Planned change in initdb-time OID allocation  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: FTI contrib
Next
From: Mike Mascari
Date:
Subject: Re: Planned change in initdb-time OID allocation