Thread: unused_oids?

Folks, 

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?

2 - 9
32
86 - 88
90
100
193 - 199
276
321 - 328
376
432 - 433
820 - 828
1004
1972 - 1973
1980
1998
2003 - 2004
2039
2096
2230
2746
2758 - 2780
2858 - 2859
2922 - 9999

Regards,
Gevik

> uuid datatype I use a script for generating catalog entries. I can close> some gaps there if the "masters" are okay
withthis. Are any OIDs> reserved for later or any range can be used in this case?
 

IMHO, better way is to use some high oids ( for example, starting from 8000 ) 
and before committing change they to lowest possible.

Ehan HEAD is under hard development, oids change quickly, so you will need to 
rearrange your oids for each snapshot.

-- 
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
  WWW: http://www.sigaev.ru/
 

Gevik Babakhani <pgdev@xs4all.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