| From: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
|---|---|
| To: | Hannu Krosing <hannuk(at)google(dot)com> |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, "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-14 06:01:28 |
| Message-ID: | CAN-LCVPauPSXSp4H2UZJnOEVoDURKiaH_Yr_cMDvJ19opn=fuw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
On this -
> Non-FULL vacuum should already work. Only commands like VACUUM FULL
> and CLUSTER which move tuples around should be disabled on TOAST
> tables.
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.
Cheers!
--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company
https://postgrespro.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2025-07-14 06:35:31 | comment in index_create "text_eq" should be "texteq" |
| Previous Message | Ashutosh Bapat | 2025-07-14 05:24:58 | Re: Report bytes and transactions actually sent downtream |