From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, 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 06:39:14 |
Message-ID: | CAH2-WzmnC_p1CQR+p3Z3BU1BXZxxT2qqQ_95kCpLy-mLMZmDUA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 5, 2019 at 11:13 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Right. Besides, adding something along the lines Michael described
> > necessitates fixing the problems that it creates. We'll run out of
> > blocks of 5 contiguous OIDs (or whatever) far sooner than we'll run
> > out of single OIDs.
>
> Well, if we ever get even close to that situation, this whole approach
> isn't really gonna work.
My point was that I don't see any reason to draw the line at or after
what Michael suggested, but before handling the exhaustion of
available blocks of 5 contiguous OIDs in the range 8000-9999. It's
just busy work.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2019-08-06 06:58:45 | Re: pgbench - implement strict TPC-B benchmark |
Previous Message | Tom Lane | 2019-08-06 06:18:26 | Re: Recent failures in IsolationCheck deadlock-hard |