Re: [HACKERS] Planned change in initdb-time OID allocation

2001-08-06 Thread Tom Lane
Mike Mascari <[EMAIL PROTECTED]> writes: > I was wondering in the past if it would simply be better to have an > .SQL script which is submitted to the template1 database at > post-initdb time with COMMENT ON statements to document built-in > types, functions, system relations, etc. The nice thing

Re: [HACKERS] Planned change in initdb-time OID allocation

2001-08-06 Thread Mike Mascari
Tom Lane wrote: > > Presently, we have hand-assigned OIDs running up to about 1950 > (according to the unused_oids script). The range up to 16K is reserved > for hand-assigned OIDs, and the OID counter starts at 16384 at initdb. > A peek in pg_database shows datlastsysoid = 18931 in current sour

Re: [HACKERS] Planned change in initdb-time OID allocation

2001-08-06 Thread Bruce Momjian
> 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_d