Re: Timeline ID hexadecimal format

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Sébastien Lardière <sebastien(at)lardiere(dot)net>, Greg Stark <stark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Timeline ID hexadecimal format
Date: 2023-03-21 07:15:22
Message-ID: e0055a8f-b4c9-399a-f1ad-29e9a934f431@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2023-03-21 07:21:36 Hash table scans outside transactions
Previous Message Andres Freund 2023-03-21 07:01:13 CREATE DATABASE ... STRATEGY WAL_LOG issues