Re: The unused_oids script should have a reminder to use the 8000-8999 OID range

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: The unused_oids script should have a reminder to use the 8000-8999 OID range
Date: 2019-08-06 04:09:49
Message-ID: CAH2-Wzm8svpgFE4bXSmnvoZhL4O+rDH5u3KjOzV75z=c=L5kjA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 5, 2019 at 8:47 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> So it would be possible to get 9998-9999 as suggestion. In which
> case, one can basically finish with this message:
> Suggested random unused OID: 9999 (1 consecutive OID(s) available
> starting here)

I strongly doubt that this will ever be a real problem. Just try again.

> Wouldn't it be better to keep some room at the end of the allowed
> array? Or at least avoid suggesting ranges where there is less than
> 3-5 OIDs available consecutively.

Not in my view. There is value in having simple, predictable behavior.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-08-06 04:20:05 Re: Remove HeapTuple and Buffer dependency for predicate locking functions
Previous Message Michael Paquier 2019-08-06 03:50:09 Re: pg can create duplicated index without any errors even warnning