Re: Timeline ID hexadecimal format
От
Peter Eisentraut
Тема
Re: Timeline ID hexadecimal format
Дата
Msg-id
e0055a8f-b4c9-399a-f1ad-29e9a934f431@enterprisedb.com
Ответ на
Re: Timeline ID hexadecimal format (Sébastien Lardière)
Список
Дерево обсуждения
Timeline ID hexadecimal format Sébastien Lardière <sebastien@lardiere.net>
Re: Timeline ID hexadecimal format Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: Timeline ID hexadecimal format Sébastien Lardière <sebastien@lardiere.net>
Re: Timeline ID hexadecimal format Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Re: Timeline ID hexadecimal format Sébastien Lardière <sebastien@lardiere.net>
Re: Timeline ID hexadecimal format Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: Timeline ID hexadecimal format Sébastien Lardière <sebastien@lardiere.net>
Re: Timeline ID hexadecimal format Greg Stark <stark@mit.edu>
Re: Timeline ID hexadecimal format Sébastien Lardière <sebastien@lardiere.net>
Re: Timeline ID hexadecimal format Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: Timeline ID hexadecimal format Sébastien Lardière <sebastien@lardiere.net>
Re: Timeline ID hexadecimal format Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: Timeline ID hexadecimal format Sébastien Lardière <sebastien@lardiere.net>
Re: Timeline ID hexadecimal format Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: Timeline ID hexadecimal format Sébastien Lardière <sebastien@lardiere.net>
Re: Timeline ID hexadecimal format Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: Timeline ID hexadecimal format Sébastien Lardière <sebastien@lardiere.net>
Re: Timeline ID hexadecimal format Sébastien Lardière <sebastien@lardiere.net>
Re: Timeline ID hexadecimal format Robert Haas <robertmhaas@gmail.com>
Re: Timeline ID hexadecimal format Sébastien Lardière <sebastien@lardiere.net>
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 по дате отправления
