Re: Why don't we have a small reserved OID range for patch revisions? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Why don't we have a small reserved OID range for patch revisions?
Date
Msg-id CA+TgmoYYrBDqNL528+ZrXvs0ro+ucAoGg1hX_sCpD__+fkxyAg@mail.gmail.com
Whole thread Raw
In response to Re: Why don't we have a small reserved OID range for patch revisions?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Feb 8, 2019 at 11:59 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> To the extent that this works at all, OIDs in the 9000 range ought
> to be enough of a flag already, I think.

A "flag" that isn't documented anywhere outside of a mailing list
discussion and that isn't checked by any code anywhere is not much of
a flag, IMHO.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages)
Next
From: Robert Haas
Date:
Subject: Re: dsa_allocate() faliure