Takahiro Itagaki <itagaki.takah...@oss.ntt.co.jp> wrote: > Could you explain why default_only entries idea is > better than adjusting those fields in the toast-specific codes? > It's my understanding that reloption-framework is just a tool to fill > reloption parameters, and it's not responsible for unused fields.
Here is my proposal to fix the issue. I didn't introduce default_only field but simply adjust parameters for TOAST reloptions. BTW, not only heap and toast relations but also btree, hash, and gist indexes use StdRdOptions. However, they actually don't support autovacuum options. So, StdRdOptions is a bloated all-in-one descriptor now. Instead, they should use fillfactor-only reloptions that is defined separately from options for heap. Regards, --- Takahiro Itagaki NTT Open Source Software Center
toast-default-only-relopts.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
