Re: Timeline ID hexadecimal format - Mailing list pgsql-hackers

From Sébastien Lardière
Subject Re: Timeline ID hexadecimal format
Date
Msg-id 1d69d7f1-6d8a-520c-0e21-609fa4fe1377@lardiere.net
Whole thread Raw
In response to Re: Timeline ID hexadecimal format  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List 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




pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Hash table scans outside transactions
Next
From: Eske Rahn
Date:
Subject: Options to rowwise persist result of stable/immutable function with RECORD result