Horton

Re: vacuum_truncate configuration parameter and isset_offset

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Nikolay Shaplov <dhyan@nataraj.su>, pgsql-hackers@lists.postgresql.org, Robert Treat <rob@xzilla.net>, Fujii Masao <masao.fujii@oss.nttdata.com>, Albe <laurenz.albe@cybertec.at>, Gurjeet Singh <gurjeet@singh.im>, Will Storey <will@summercat.com>, Álvaro Herrera <alvherre@alvh.no-ip.org>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2025-03-24T14:48:25Z
Lists: pgsql-hackers 
On Mon, Mar 24, 2025 at 10:43 AM Nathan Bossart
<nathandbossart@gmail.com> wrote:
> Overall, the biggest reason I didn't proceed with the enum is because it
> felt like it was making it the user's problem.  Rather than just teaching
> our code how to determine if a reloption was explicitly set, we'd be
> introducing unnecessary complexity to the user, or at least we'd be trying
> to closely match the existing functionality in an attempt to hide this
> complexity from them.

+1. Giving the user the ability to set the option to a value called
"unset" doesn't seem right to me.

-- 
Robert Haas
EDB: http://www.enterprisedb.com