From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gevik Babakhani <pgdev(at)xs4all(dot)nl> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: unused_oids? |
Date: | 2007-01-25 16:16:12 |
Message-ID: | 20152.1169741772@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gevik Babakhani <pgdev(at)xs4all(dot)nl> writes:
> At this moment the following is the list of the unused OIDs. For the
> uuid datatype I use a script for generating catalog entries. I can close
> some gaps there if the "masters" are okay with this. Are any OIDs
> reserved for later or any range can be used in this case?
My advice is not to try to fill in the gaps --- better to leave them
there so that if any other objects are created that're related to the
nearby ones, they can be assigned nearby OIDs. If you've got a patch
that is going to use a bunch of OIDs for related purposes, it's better
to use a contiguous chunk of OIDs for it.
I believe that the bitmap-indexing patch is using OIDs starting at 3000
(at least that's the advice I gave them awhile back). If you need less
than 50 you might start at 2950, else check that patch and start above
whatever they used.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-01-25 16:22:33 | Re: Proposal: allow installation of any contrib module simultaneously with Postgres itself |
Previous Message | Teodor Sigaev | 2007-01-25 16:15:15 | Re: tsearch in core patch, for inclusion |