Horton
Menu

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

Andrey Borodin <x4mmm@yandex-team.ru>

View thread
From: "Andrey M. Borodin" <x4mmm@yandex-team.ru>
To: John Naylor <john.naylor@enterprisedb.com>
Cc: Jakub Wartak <jakub.wartak@enterprisedb.com>, Nikita Malakhov <hukutoc@gmail.com>, Gurjeet Singh <gurjeet@singh.im>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2024-03-28T12:09:30Z
Lists: 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 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?

Thanks!


Best regards, Andrey Borodin.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Document limit on the number of out-of-line values per table

  2. Log when GetNewOidWithIndex() fails to find unused OID many times.