aboutsummaryrefslogtreecommitdiff
path: root/contrib/intarray/_int_gist.c
diff options
context:
space:
mode:
authorPeter Geoghegan <pg@bowt.ie>2019-08-05 11:47:34 -0700
committerPeter Geoghegan <pg@bowt.ie>2019-08-05 11:47:34 -0700
commit98eab30b93d52a114bd65e154cda3402d0630667 (patch)
treeea41649657cef227c2ac02d711a55ed90a1b4b83 /contrib/intarray/_int_gist.c
parent4766dce0dd1a1a26db253dfc81773a2c55cd2555 (diff)
downloadpostgresql-98eab30b93d52a114bd65e154cda3402d0630667.tar.gz
postgresql-98eab30b93d52a114bd65e154cda3402d0630667.zip
Show specific OID suggestion in unused_oids output.
Commit a6417078 established a new project policy around OID assignment: new patches are encouraged to choose a random OID in the 8000..9999 range when a manually-assigned OID is required (if multiple OIDs are required, a consecutive block of OIDs starting from the random point should be used). Catalog entries added by committed patches that use OIDs from this "unstable" range are renumbered after feature freeze. This practice minimizes OID collisions among concurrently-developed patches. Show a specific random OID suggestion when the unused_oids script is run. This makes it easy for patch authors to use a random OID from the unstable range, per the new policy. Author: Julien Rouhaud, Peter Geoghegan Reviewed-By: Tom Lane Discussion: https://postgr.es/m/CAH2-WzkkRs2ScmuBQ7xWi7xzp7fC1B3w0Nt8X+n4rBw5k+Z=zA@mail.gmail.com
Diffstat (limited to 'contrib/intarray/_int_gist.c')
0 files changed, 0 insertions, 0 deletions