Re: problems with toast.* reloptions - Mailing list pgsql-hackers

From Nikita Malakhov
Subject Re: problems with toast.* reloptions
Date
Msg-id CAN-LCVOCk0hcqcu3Fw1LSVYecmQD1J26YNGuc=sybN=ds=WpPg@mail.gmail.com
Whole thread
In response to Re: problems with toast.* reloptions  (solai v <solai.cdac@gmail.com>)
Responses Re: problems with toast.* reloptions
List pgsql-hackers
Hi hackers!

I strongly object to removing TOAST reloptions.
As anyone here knows, TOAST tables are subject to bloating, and in my opinion
we'll eventually come to multi TOAST tables per relation.
I've tested such an approach some time ago, it does not create any problems
and provides additional possibilities like ability to vacuum separate TOAST
only partly influencing overall work with parent relation.

On Tue, Jun 2, 2026 at 12:42 PM solai v <solai.cdac@gmail.com> wrote:
Hi,
> I humbly encourage you to read the rest of the thread.  In particular, I'm
> curious whether anyone would object to removing the TOAST reloptions.
I tested the remove-toast-reloptions.patch on current HEAD.
The patch applied and built cleanly .I verified that TOAST reloptions
are no longer accepted:
ALTER TABLE toat_test SET (toast.vacuum_truncate=false):
ALTER TABLE toast_test SET(toast.autovacuum_enabled = false);
Both returned:
ERROR:unrecognized parameter namespace "toast"
Regular reloptions still work as expected:
ALTER TABLE toast_test SET (vacuum_truncate=false);
The patch behaved as expected in my testing

Regards
solai




--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company

pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Re: Heads Up: cirrus-ci is shutting down June 1st
Next
From: Chao Li
Date:
Subject: SERVICEFILE shows wrong file after servicefile fallback