Re: Last builtin OID?

At 21:40 21/10/00 -0400, Tom Lane wrote:
>We could implement
>this by initializing the OID counter at 16384 as now, and then rewriting
>it to 32768 at the end of initdb.
...
>BTW, this raises a point I'd never thought hard about: if the dbadmin
>adds some site-local objects to template1, then makes databases that
>copy these objects, a pg_dumpall and restore will do the Wrong Thing.

Some kind of forced value would be good, although I would prefer the
'CREATE DATABASE' code to set a value in a table somewhere to the last OID
used when the DB was created. This would deal with the 'extended template1'
scenario (which, incidentally, I am already a victim of). Could a new
attribute be added to pg_database?


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 0500 83 82 82         |                 ___________ |
Http://www.rhyme.com.au          |                /           \|                                |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/