| From: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
| Cc: | Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, Nikita Malakhov <hukutoc(at)gmail(dot)com>, Gurjeet Singh <gurjeet(at)singh(dot)im>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Doc limitation update proposal: include out-of-line OID usage per TOAST-ed columns |
| Date: | 2024-03-28 12:09:30 |
| Message-ID: | E85003BA-8F2D-469E-B5FB-CB1CB09E6B4B@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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?
Thanks!
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey M. Borodin | 2024-03-28 12:16:17 | Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector |
| Previous Message | Tender Wang | 2024-03-28 12:05:04 | Re: Can't find not null constraint, but \d+ shows that |