From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Release notes on "reserved OIDs"
Date: Wed, 04 Sep 2019 11:11:23 -0400
Message-ID: <2687.1567609883@sss.pgh.pa.us> (raw)
In-Reply-To: <20190904150005.ncwlp3gxwp7n55ja@alap3.anarazel.de>
References: <20190830153424.GA3324@alvherre.pgsql>
<29753.1567182909@sss.pgh.pa.us>
<20190904094055.og3vq27tj7we7x4n@alap3.anarazel.de>
<22548.1567604503@sss.pgh.pa.us>
<20190904150005.ncwlp3gxwp7n55ja@alap3.anarazel.de>
Andres Freund <andres@anarazel.de> writes:
> On 2019-09-04 09:41:43 -0400, Tom Lane wrote:
>> As things stand after a6417078c, the safest place for a fork to put
>> private OIDs is actually from 7999 down; patches shouldn't touch that
>> range, and it'll be a long time till we hit it working up.
> Should we just update the comment to reference that then?
WFM.
I'm planning to make a pass over the release notes soon, and will
update this one when I get to it.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, alvherre@2ndquadrant.com, bruce@momjian.us, pgsql-docs@lists.postgresql.org
Subject: Re: Release notes on "reserved OIDs"
In-Reply-To: <2687.1567609883@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox