Horton

Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem)

Michael Paquier <michael@paquier.xyz>

View thread
From: Michael Paquier <michael@paquier.xyz>
To: Nikita Malakhov <hukutoc@gmail.com>
Cc: Hannu Krosing <hannuk@google.com>, Álvaro Herrera <alvherre@kurilemu.de>, "Burd, Greg" <greg@burd.me>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-15T00:55:54Z
Lists: pgsql-hackers

Commits

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

  1. Add data type oid8, 64-bit unsigned identifier

On Mon, Jul 14, 2025 at 09:01:28AM +0300, Nikita Malakhov wrote:
> Cool, toast tables are subject to bloating in update-heavy scenarios
> and it's a big problem in production systems, it seems there is a promising
> way to solve it once and for all!
> 
> Have to mention though that we encountered issues in logical replication
> when we made toast values updatable.
> 
> Also researching direct tids implementation.

I would be curious to see if the refactoring done on this thread would
be useful in the scope of what you are trying to do.  I'd suggest
dropping that on a different thread, though, if you finish with a
patch or something worth looking at for others.
--
Michael