Postgres Pro
Downloads
Home   >   mailing lists

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

From Peter Geoghegan
Subject Re: Why don't we have a small reserved OID range for patch revisions?
Date
Msg-id CAH2-WzkC0nV+-2h+yQXSfRGoxr0D1c+eNTS2qKD6gapV0NFnFA@mail.gmail.com
Whole thread Raw
In response to Re: Why don't we have a small reserved OID range for patch revisions?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Why don't we have a small reserved OID range for patch revisions?
List pgsql-hackers
Tree view 
On Wed, Feb 27, 2019 at 2:44 PM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> If this is the problem (although I think we'd find that OID collisions
> are rather rare compared to other gratuitous cfbot failures), why not
> have the cfbot build with a flag that ignores OID collisions?

How would that work?

-- 
Peter Geoghegan

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Why don't we have a small reserved OID range for patch revisions?
Next
From: Tom Lane
Date:
Subject: Re: Why don't we have a small reserved OID range for patch revisions?