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

From Nathan Bossart
Subject Re: problems with toast.* reloptions
Date
Msg-id aFl598epAdUrrv0y@nathan
Whole thread Raw
In response to Re: problems with toast.* reloptions  (shihao zhong <zhong950419@gmail.com>)
List pgsql-hackers
On Sat, Jun 21, 2025 at 11:45:25PM -0400, shihao zhong wrote:
> 2) When updating a table's relopt, also update the relopt of its
> associated TOAST table if it's not already set. Similarly, when
> creating a new TOAST table, it would inherit the parent's relopt.
> 
> Option 2 seems more reasonable to me, as it avoids requiring customers
> to manually resolve these options, when they have different settings
> for the parent and TOAST tables."

I like this one, but since it won't fix existing clusters, it might only be
workable for v19.

-- 
nathan



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Improve CRC32C performance on SSE4.2
Next
From: Jacob Champion
Date:
Subject: Re: BackendKeyData is mandatory?