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

Michael Paquier <michael@paquier.xyz>

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-19T05:04:52Z

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 →

Add data type oid8, 64-bit unsigned identifier
- b139bd3b6ef0 19 (unreleased) landed

On Fri, Jul 18, 2025 at 10:24:12PM +0300, Nikita Malakhov wrote:
> I'm currently debugging POC direct tids TOAST patch (on top of your branch),
> will mail it in a day or two.

Interesting.  Of course I may be wrong because I have no idea of how
you have shaped things, still I suspect that for the basics you should
just need 0003, 0004, the parts with the GUC to switch the TOAST table
type and the dump/restore/upgrade bits.
--
Michael