On Fri, Oct 3, 2014 at 3:06 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> It's not important enough to go back and change catversion.h now, but
> please keep it in mind for the future. One of the main values of
> catversion is to prevent developers from wasting time chasing regression
> test failures that are just code-vs-data-skew issues.
It would be nice to institutionalize the idea of "private OIDs", too,
each represented by constants like PG_PRIVATE_OID_ONE (it would
probably go up to TEN, or thereabouts). Fixing duplicates when
rebasing a patch is something that we could thereby avoid - It would
become the responsibility of the committer to adjust the OIDs to
conventional "public OIDs" before pushing to the master branch, just
like it is currently left to the commiter to bump catversion. That
work could even be scripted, I think.
I like picking pg_proc OIDs that are at the beginning of some unused
range, and so do other people, so this happens more often than you
might think.
--
Peter Geoghegan