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

Hi Andrey,

On Thu, Mar 28, 2024 at 1:09 PM Andrey M. Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>
>
>
> > On 8 Aug 2023, at 12:31, John Naylor <john(dot)naylor(at)enterprisedb(dot)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 whole OID 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 is more 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?

Yes; I've forgotten about this one and clearly I had problems
formulating it in proper shape to be accepted. I've moved it to the
next CF now as this is not critical and I would prefer to help current
timesenistive CF. Anyone is welcome to help amend the patch...

-J.