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

Jim Nasby <jnasby@upgrade.com>

From: Jim Nasby <jnasby@upgrade.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: "Burd, Greg" <greg@burd.me>, Nikita Malakhov <hukutoc@gmail.com>, Hannu Krosing <hannuk@google.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-08-04T19:37:19Z
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 Fri, Aug 1, 2025 at 4:03 AM Michael Paquier <michael@paquier.xyz> wrote:

> - Addition of separate patch to rename varatt_external to
> varatt_external_oid and VARTAG_ONDISK to VARTAG_ONDISK_OID, in 0003.
>

Since you're already renaming things... ISTM "ondisk" has the potential for
confusion, assuming that at some point we'll have the ability to store
large datums directly in the filesystem (instead of breaking into chunks to
live in a relation). VARTAG_DURABLE might be a better option.