Horton

Re: vacuum_truncate configuration parameter and isset_offset

Nathan Bossart <nathandbossart@gmail.com>

View thread
From: Nathan Bossart <nathandbossart@gmail.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Nikolay Shaplov <dhyan@nataraj.su>, Álvaro Herrera <alvherre@alvh.no-ip.org>, "pgsql-hackers@lists.postgresql.org" <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>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2025-03-26T15:28:26Z
Lists: pgsql-hackers 
On Wed, Mar 26, 2025 at 08:09:53AM -0700, David G. Johnston wrote:
> I'm willing to say "I don't know why this is so very important to Nikolay,
> but I trust him that it is, and since my opinion isn't that strong and this
> isn't a big deal, so I will accommodate the person screaming that adding
> this will make their life miserable in a real way."  Maybe others need more
> evidence of what that misery looks like?

To summarize the discussion thus far, Robert and I seem to be okay with
isset_offset, David is leaning no (+.25 yes and -.75 no), and Niolay and
Álvaro appear to favor an enum approach, which would look like this [0].
That's +2.25 and -2.75.

Is that an accurate analysis of where folks stand?

[0] https://postgr.es/m/attachment/174762/v2-0001-change-vacuum_truncate-relopt-to-enum.patch

-- 
nathan