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

John Naylor <johncnaylorls@gmail.com>

From: John Naylor <johncnaylorls@gmail.com>

To: Jakub Wartak <jakub.wartak@enterprisedb.com>

Cc: Robert Haas <robertmhaas@gmail.com>, "Andrey M. Borodin" <x4mmm@yandex-team.ru>, Nikita Malakhov <hukutoc@gmail.com>, Gurjeet Singh <gurjeet@singh.im>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2024-08-20T07:03:13Z

Lists: pgsql-hackers

On Mon, Aug 12, 2024 at 11:01 AM John Naylor <johncnaylorls@gmail.com> wrote:
>
> Extra explicitness might be good. "Response time" seems like a
> networking concept, so possibly ", in turn slowing down INSERT/UPDATE
> statements." I'm inclined to commit that way in a couple days, barring
> further comments.

This is done.

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