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: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "Burd, Greg" <greg@burd.me>, Nikita Malakhov <hukutoc@gmail.com>, Hannu Krosing <hannuk@google.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-12-18T05:40:24Z
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, Dec 11, 2025 at 07:47:05AM +0900, Michael Paquier wrote:
> On Mon, Dec 08, 2025 at 04:19:54PM -0500, Robert Haas wrote:
> > I took a brief look at this today, looking at parts of v8-0005 and
> > v8-0015.
> 
> Thanks for the input!

The CF bot was complaining that this patch set needed a rebase due to
the recent changes in pg_resetwal, so here we go.  For now this is the
same stuff as the previous versions, with the same separation and
design.

I am also looking at what it would take to implement what the brutal
approach I have mentioned upthread.  This requires a bit more
reorganization than what I had in mind initially.  By putting first in
the patch set some of the parts that are kind of relevant with the two
designs, things seem to be a bit leaner.  I need to spend a few more
hours on that beforebeing sure, though..

For now, rebase for a happy bot.
--
Michael