| From: | solai v <solai(dot)cdac(at)gmail(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: problems with toast.* reloptions |
| Date: | 2026-06-02 09:42:10 |
| Message-ID: | CAF0whucUigX5c2_rAeDNKNXp-L6nJF4Td83opO1i2xBDNNPOvw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2026-06-02 10:01:07 | RE: pg_createsubscriber: allow duplicate publication names |
| Previous Message | Chao Li | 2026-06-02 09:17:18 | Re: pg_createsubscriber: allow duplicate publication names |