Re: pg_resetwal: Fix handling of commit timestamp XIDs - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: pg_resetwal: Fix handling of commit timestamp XIDs
Date
Msg-id 9f16d092-cf92-4524-b349-3146e02ddb67@iki.fi
Whole thread
In response to pg_resetwal: Fix handling of commit timestamp XIDs  (Chao Li <li.evan.chao@gmail.com>)
List pgsql-hackers
On 29/09/2026 09:09, Chao Li wrote:
> Hi,
> 
> While working on patch [1], I spotted two small issues in pg_resetwal.
> 
> 1. The -c option accepts two XIDs. The first is parsed by strtouint32_strict(), but the second is parsed by
strtoul().This seems to be an oversight in 636c1914b48, which introduced strtouint32_strict().
 
> 
> 2. The help message for the -c option says that “zero means no change”, but this behavior is missing on the current
masterbranch. I checked the git history, and the behavior was lost in 978cf02bb8c, which added separate “given” flags
forcommand-line options.
 
> 
> The fixes for both issues are tiny. See the attached patch for details.
> 
> Unfortunately, I reviewed both patches but didn't notice these issues at the time. Both commits were included in
PG19,so this might be worth back-patching to 19.
 

Pushed, thanks!

- Heikki




pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers
Next
From: "Matheus Alcantara"
Date:
Subject: Re: [PATCH v1] Fix for Bug#19724 - ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check