Request a Demo
Home   >   mailing lists

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

From Bertrand Drouvot
Subject Re: pg_resetwal prints new OldestXID in wrong circumstances
Date
Msg-id aR2WWN6fW/8BFOkx@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to pg_resetwal prints new OldestXID in wrong circumstances  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: pg_resetwal prints new OldestXID in wrong circumstances
List pgsql-bugs
Tree view 
Hi,

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!

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

pgsql-bugs by date:

Previous
From: "S, Naveen Krishna (Development Engineer 3)"
Date:
Subject: Re: [EXTERNAL] Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors
Next
From: Richard Guo
Date:
Subject: Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)