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

From Peter Eisentraut
Subject Re: Timeline ID hexadecimal format
Date
Msg-id e0055a8f-b4c9-399a-f1ad-29e9a934f431@enterprisedb.com
Whole thread Raw
In response to Re: Timeline ID hexadecimal format  (Sébastien Lardière <sebastien@lardiere.net>)
Responses Re: Timeline ID hexadecimal format  (Sébastien Lardière <sebastien@lardiere.net>)
List 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




pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: CREATE DATABASE ... STRATEGY WAL_LOG issues
Next
From: Ashutosh Bapat
Date:
Subject: Hash table scans outside transactions