Re: vacuum_truncate configuration parameter and isset_offset

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Nikolay Shaplov <dhyan(at)nataraj(dot)su>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(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 19:26:17
Message-ID: Z-Gx2WItrTKUopIM@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 24, 2025 at 10:12:05PM +0300, Nikolay Shaplov wrote:
> And second general idea: changing engine is bad, at least when you can manage
> without changing it.

You have asserted this a couple of times without providing any reasons why.
I know of no general project policy about changing the reloption code. I
would expect this code to evolve just like any other part of Postgres,
whether it's to improve performance or to expand the feature set.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikolay Shaplov 2025-03-24 19:30:41 Re: vacuum_truncate configuration parameter and isset_offset
Previous Message Alena Rybakina 2025-03-24 19:21:24 Re: Proposal - Allow extensions to set a Plan Identifier