Horton

Re: Timeline ID hexadecimal format

Sébastien Lardière <sebastien@lardiere.net>

View thread View on postgr.es
From: Sébastien Lardière <sebastien@lardiere.net>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Greg Stark <stark@mit.edu>, pgsql-hackers@postgresql.org
Date: 2023-03-21T07:37:45Z
Lists: pgsql-hackers 
On 21/03/2023 08:15, Peter Eisentraut wrote:
> 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
>
thanks,


-- 
Sébastien

Commits

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

  2. doc: Additional information about timeline ID hexadecimal format