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

David Rowley <dgrowleyml@gmail.com>

From: David Rowley <dgrowleyml@gmail.com>

To: Gurjeet Singh <gurjeet@singh.im>

Cc: Nikita Malakhov <hukutoc@gmail.com>, Jakub Wartak <jakub.wartak@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2023-04-26T11:48:30Z

Lists: pgsql-hackers

On Sun, 23 Apr 2023, 3:42 am Gurjeet Singh, <gurjeet@singh.im> wrote:

> I anticipate that edits to Appendix K Postgres Limits will prompt
> improving the note in there about the maximum column limit, That note
> is too wordy, and sometimes confusing, especially for the audience
> that it's written for: newcomers to Postgres ecosystem.
>

I doubt it, but feel free to submit a patch yourself which improves it
without losing the information which the paragraph is trying to convey.

David

>

Commits

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

Document limit on the number of out-of-line values per table
- e51160fa0bab 15.9 landed
- dda341b32c88 14.14 landed
- c9aa6f4f86fc 13.17 landed
- 667401dd40c8 17.0 landed
- 5ff394503ce2 12.21 landed
- 4d93bbd4e0d4 18.0 landed
- 409be33c3136 16.5 landed
Log when GetNewOidWithIndex() fails to find unused OID many times.
- 7fbcee1b2d5f 14.0 cited