Re: Timeline ID hexadecimal format
Sébastien Lardière <sebastien@lardiere.net>
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-20T09:40:31Z
Lists: pgsql-hackers
On 20/03/2023 09:17, Peter Eisentraut wrote: > I have committed the two documentation changes, with some minor > adjustments. Thank you, > > On 07.03.23 18:14, Sébastien Lardière wrote: >>>>> Maybe this could be fixed instead? >>>> >>>> Indeed, and strtoul is probably a better option than sscanf, don't >>>> you think ? >>> >>> Yeah, the use of sscanf() is kind of weird here. We have been >>> moving the option parsing to use option_parse_int(). Maybe hex >>> support could be added there. Or just use strtoul(). >> >> >> I've made the change with strtoul >> >> 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 thank you, -- Sébastien
Commits
-
pg_waldump: Allow hexadecimal values for -t/--timeline option
- 4c8044c04455 16.0 landed
-
doc: Additional information about timeline ID hexadecimal format
- 0b51d423e974 16.0 landed