| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: problems with toast.* reloptions |
| Date: | 2026-05-01 21:41:12 |
| Message-ID: | afUd-A4CvaGc9se7@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 24, 2025 at 11:38:41AM -0500, Nathan Bossart wrote:
> Yeah, I'm tempted to even ask how folks feel about removing the toast.*
> reloptions. Maybe there's some simple cases that work well enough, but
> AFAICT any moderately-complicated setup basically doesn't work at all. In
> any case, writing out this patch set has got me on the fix-on-HEAD-only
> bandwagon.
For the sake of discussion, I wrote a patch for this. I suggested removing
toast.* relopts to some colleagues recently, and nobody was aware of much
(if any) use in the field. So maybe this isn't totally
out-of-the-question...
--
nathan
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-remove-toast-reloptions.patch | text/plain | 47.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-05-01 22:43:44 | Re: Refactor code around GUC default_toast_compression |
| Previous Message | Daniel Gustafsson | 2026-05-01 21:13:16 | Re: Changing the state of data checksums in a running cluster |