Horton

Re: Timeline ID hexadecimal format

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Sébastien Lardière <sebastien@lardiere.net>, Greg Stark <stark@mit.edu>, pgsql-hackers@postgresql.org
Date: 2023-03-21T07:15:22Z
Lists: pgsql-hackers 
On 20.03.23 10:40, Sébastien Lardière wrote:
>>> About option_parse_int(), actually, strtoint() is used, do we need a 
>>> option_parse_ul() fonction ?
>>
>> For the option parsing, I propose the attached patch.  This follows 
>> the structure of option_parse_int(), so in the future it could be 
>> extracted and refactored in the same way, if there is more need.
> 
> 
> ok for me, it accept 0x values and refuse wrong values

committed

Commits

  1. pg_waldump: Allow hexadecimal values for -t/--timeline option

  2. doc: Additional information about timeline ID hexadecimal format