pgsql: Change oddly-chosen OID allocation.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Change oddly-chosen OID allocation.
Date: 2018-03-21 18:57:19
Message-ID: E1eyivH-0004hl-7Q@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Change oddly-chosen OID allocation.

I noticed while fooling with John Naylor's bootstrap-data patch that we had
one high-numbered manually assigned OID, 8888, which evidently came from a
submission that the committer didn't bother to bring into line with usual
OID allocation practices before committing. That's a bad idea, because it
creates a hazard for other patches that may be temporarily using high OID
numbers. Change it to something more in line with what we usually do.

This evidently dates to commit abb173392. It's too late to change it
in released branches, but we can fix it in HEAD.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/27ba260c739e4e10e28688993208c3ffa1b469ab

Modified Files
--------------
src/include/catalog/catversion.h | 2 +-
src/include/catalog/pg_proc.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-03-21 22:30:51 pgsql: Improve predtest.c's handling of cases with NULL-constant inputs
Previous Message Peter Eisentraut 2018-03-21 16:21:47 pgsql: pg_controldata: Prevent division-by-zero errors