Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem)
| От | Nikita Malakhov |
|---|---|
| Тема | Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) |
| Дата | |
| Msg-id | CAN-LCVPGoSrf46i3GrMhyuY7ngvO48CAn+PXeR4EC8d5phZzQg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem)
Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) |
| Список | 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@paquier.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
В списке pgsql-hackers по дате отправления: