Re: Timeline ID hexadecimal format

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


In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Eske Rahn 2023-03-21 07:38:12 Options to rowwise persist result of stable/immutable function with RECORD result
Previous Message Ashutosh Bapat 2023-03-21 07:21:36 Hash table scans outside transactions