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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Burd, Greg" <greg(at)burd(dot)me>, Nikita Malakhov <hukutoc(at)gmail(dot)com>, Hannu Krosing <hannuk(at)google(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem)
Date: 2026-01-04 22:23:23
Message-ID: aVroWyJ3Cy9ZLzkj@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 18, 2025 at 02:40:24PM +0900, Michael Paquier wrote:
> 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..

I am still working on redesigning the patch set to avoid the pointer
redirection and the callbacks assigned to the vartags.

One thing that stands out for me is that I am going to need the oid8
data type anyway, to be store the 8-byte values in the catalogs, with
a C type to mark some of the TOAST apis with it across the board, so I
would like to apply that to move this part out of the way (0001 only)
and move the needle. If there are any objections to that, please feel
free.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-01-04 23:02:22 Re: Typos in the code and README
Previous Message David E. Wheeler 2026-01-04 20:51:41 Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part