Horton

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

Álvaro Herrera <alvherre@kurilemu.de>

View thread
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Hannu Krosing <hannuk@google.com>
Cc: Michael Paquier <michael@paquier.xyz>, "Burd, Greg" <greg@burd.me>, Nikita Malakhov <hukutoc@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-08T19:37:00Z
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 2025-Jul-08, Hannu Krosing wrote:

> I still think we should go with direct toast tid pointers in varlena
> and not some kind of oid.

I think this can be made to work, as long as we stop seeing the toast
table just like a normal heap table containing normal tuples.  A lot to
reimplement though -- vacuum in particular.  Maybe it can be thought of
as a new table AM.  Not an easy project, I reckon.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/