From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: an OID >= 8000 in master |
Date: | 2019-11-21 02:07:12 |
Message-ID: | CAH2-Wznchx6GB8mH_1siPej668nrCPMuPJ_D+Xr+PTt5s0sc2A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Nov 20, 2019 at 5:44 PM Kyotaro Horiguchi
<horikyota(dot)ntt(at)gmail(dot)com> wrote:
> I happened to find that the commit 71dcd74 added the function
> "network_sortsupport" with OID = 8190. Is it right? Otherwise we
> should we move it to, say, 4035.
>
> (I understand that OID [8000, 9999] are development-use.)
I committed this patch using an OID in that range intentionally.
Commit a6417078 established a new project policy around OID
assignment. It will be renumbered at the end of the release cycle.
The unused_oids script will now actively suggest that patch authors
use a particular random OID from this range, so this will probably be
very common soon.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2019-11-21 02:10:09 | Re: an OID >= 8000 in master |
Previous Message | Michael Paquier | 2019-11-21 02:06:52 | Re: an OID >= 8000 in master |