Re: vacuum_truncate configuration parameter and isset_offset - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: vacuum_truncate configuration parameter and isset_offset
Date
Msg-id Z-GPPoK9lMmSeAXE@nathan
Whole thread Raw
In response to Re: vacuum_truncate configuration parameter and isset_offset  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: vacuum_truncate configuration parameter and isset_offset
List pgsql-hackers
On Mon, Mar 24, 2025 at 09:40:24AM -0700, David G. Johnston wrote:
> So, given the precedent of vacuum_index_cleanup and the above, we should
> turn this into an enum that accepts all existing boolean literal inputs and
> also has a undocumented "unset" default value that the user is not allowed
> to explicitly set but instead only gets used to resolve an unset reloption
> at runtime.

This would involve adding a field to relopt_enum_elt_def to declare a value
as "unsettable," right?  That seems feasible, but IMHO it's comparable to
adding a field to reopt_parse_elt.

-- 
nathan



pgsql-hackers by date:

Previous
From: Alexander Pyhalov
Date:
Subject: Re: Add semi-join pushdown to postgres_fdw
Next
From: Nikolay Shaplov
Date:
Subject: Re: vacuum_truncate configuration parameter and isset_offset