Re: vacuum_truncate configuration parameter and isset_offset

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Nikolay Shaplov <dhyan(at)nataraj(dot)su>, Robert Haas <robertmhaas(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Robert Treat <rob(at)xzilla(dot)net>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Albe <laurenz(dot)albe(at)cybertec(dot)at>, Gurjeet Singh <gurjeet(at)singh(dot)im>, Will Storey <will(at)summercat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: vacuum_truncate configuration parameter and isset_offset
Date: 2025-03-24 16:08:18
Message-ID: CAKFQuwbNmMHny1LpV1eN91UySO8Za2=M2BF3W60qrq3x5LCdjA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 24, 2025 at 9:00 AM Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
wrote:

> Hello
>
> I don't understand why this shouldn't work exactly like
> vacuum_index_cleanup (cf. vacuum_rel lines 2170ff). That would require
> no new mechanism.
>
>
That reloption is already an enum and there is no GUC to defer to when the
value is unset. It doesn't seem like an equivalent scenario. AUTO is a
perfectly useful value as opposed to an undocumented sentinel for
unset/missing.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2025-03-24 16:14:46 Re: BitmapHeapScan streaming read user and prelim refactoring
Previous Message Nikolay Shaplov 2025-03-24 16:06:51 Re: vacuum_truncate configuration parameter and isset_offset