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-Gx2WItrTKUopIM@nathan
Whole thread Raw
In response to Re: vacuum_truncate configuration parameter and isset_offset  (Nikolay Shaplov <dhyan@nataraj.su>)
Responses Re: vacuum_truncate configuration parameter and isset_offset
List 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



pgsql-hackers by date:

Previous
From: Alena Rybakina
Date:
Subject: Re: Proposal - Allow extensions to set a Plan Identifier
Next
From: Nikolay Shaplov
Date:
Subject: Re: vacuum_truncate configuration parameter and isset_offset