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

From solai v
Subject Re: problems with toast.* reloptions
Date
Msg-id CAF0whucUigX5c2_rAeDNKNXp-L6nJF4Td83opO1i2xBDNNPOvw@mail.gmail.com
Whole thread
In response to Re: problems with toast.* reloptions  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: problems with toast.* reloptions
List 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



pgsql-hackers by date:

Previous
From: Nisha Moond
Date:
Subject: Re: Support EXCEPT for TABLES IN SCHEMA publications
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: pg_createsubscriber: allow duplicate publication names