Re: Doc limitation update proposal: include out-of-line OID usage per TOAST-ed columns - Mailing list pgsql-hackers

From Andrey M. Borodin
Subject Re: Doc limitation update proposal: include out-of-line OID usage per TOAST-ed columns
Date
Msg-id E85003BA-8F2D-469E-B5FB-CB1CB09E6B4B@yandex-team.ru
Whole thread Raw
In response to Re: Doc limitation update proposal: include out-of-line OID usage per TOAST-ed columns  (John Naylor <john.naylor@enterprisedb.com>)
Responses Re: Doc limitation update proposal: include out-of-line OID usage per TOAST-ed columns
List pgsql-hackers

> On 8 Aug 2023, at 12:31, John Naylor <john.naylor@enterprisedb.com> wrote:
>
> > > Also the shared counter is the cause of the slowdown, but not the reason for the numeric limit.
> >
> > Isn't it both? typedef Oid is unsigned int = 2^32, and according to GetNewOidWithIndex() logic if we exhaust the
wholeOID space it will hang indefinitely which has the same semantics as "being impossible"/permanent hang (?) 
>
> Looking again, I'm thinking the OID type size is more relevant for the first paragraph, and the shared/global aspect
ismore relevant for the second. 
>
> The last issue is how to separate the notes at the bottom, since there are now two topics.

Jakub, do you have plans to address this feedback? Is the CF entry still relevant?

Thanks!


Best regards, Andrey Borodin.


pgsql-hackers by date:

Previous
From: Tender Wang
Date:
Subject: Re: Can't find not null constraint, but \d+ shows that
Next
From: "Andrey M. Borodin"
Date:
Subject: Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector