From: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Hannu Krosing <hannuk(at)google(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, "Burd, Greg" <greg(at)burd(dot)me>, 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: | 2025-07-18 19:24:12 |
Message-ID: | CAN-LCVPGoSrf46i3GrMhyuY7ngvO48CAn+PXeR4EC8d5phZzQg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Michael,
I'm currently debugging POC direct tids TOAST patch (on top of your branch),
will mail it in a day or two.
On Tue, Jul 15, 2025 at 3:56 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Mon, Jul 14, 2025 at 09:01:28AM +0300, Nikita Malakhov wrote:
> > Cool, toast tables are subject to bloating in update-heavy scenarios
> > and it's a big problem in production systems, it seems there is a
> promising
> > way to solve it once and for all!
> >
> > Have to mention though that we encountered issues in logical replication
> > when we made toast values updatable.
> >
> > Also researching direct tids implementation.
>
> I would be curious to see if the refactoring done on this thread would
> be useful in the scope of what you are trying to do. I'd suggest
> dropping that on a different thread, though, if you finish with a
> patch or something worth looking at for others.
> --
> Michael
>
--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company
https://postgrespro.ru/
From | Date | Subject | |
---|---|---|---|
Next Message | Sami Imseih | 2025-07-18 19:37:09 | Re: track generic and custom plans in pg_stat_statements |
Previous Message | Noah Misch | 2025-07-18 19:17:02 | Re: Test instability when pg_dump orders by OID |