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: Tom Lane <tgl@sss.pgh.pa.us>
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-09-16T05:14:43Z
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

Attachments

On Thu, Aug 14, 2025 at 02:49:06PM +0900, Michael Paquier wrote:
> I have dropped the amcheck test patch for now, which was fun but it's
> not really necessary for the "basics".  I have done also more tests,
> playing for example with pg_resetwal, installcheck and pg_upgrade
> scenarios.  I am wondering if it would be worth doing a pg_resetwal in
> the node doing an installcheck on the instance to be upgraded, bumping
> its next OID to be much larger than 4 billion, actually..

Four patches had conflicts with 748caa9dcb68, so rebased as v6.
--
Michael