Re: pg_resetwal prints new OldestXID in wrong circumstances - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: pg_resetwal prints new OldestXID in wrong circumstances
Date
Msg-id 638e63ba-b8a3-4236-9c48-0d4a5ef2f034@iki.fi
Whole thread Raw
In response to Re: pg_resetwal prints new OldestXID in wrong circumstances  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
List pgsql-bugs
On 19/11/2025 12:05, Bertrand Drouvot wrote:
> On Wed, Nov 19, 2025 at 11:52:31AM +0200, Heikki Linnakangas wrote:
>> Printing the new OldestXID value is incorrectly tied to whether the
>> --next-transaction-id option is given, so this prints it, even though
>> OldestXID is not being modified:
> 
> Nice catch!
> 
>> This seems to have been an oversight when the --oldest-transaction-id option
>> was added (commit 74cf7d46a91d).
> 
> yeah.
> 
>> Before that, OldestXID was reset when the
>> --next-transaction-id option was given.
>>
>> Fix attached. Barring objections, I will commit and backpatch this.
> 
> LGTM, thanks!

Committed, thanks!

- Heikki




pgsql-bugs by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Re: BUG #19095: Test if function exit() is used fail when linked static
Next
From: Thomas Munro
Date:
Subject: Re: [EXTERNAL] Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors