Re: Range checks of pg_test_fsync --secs-per-test and pg_test_timing --duration

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Range checks of pg_test_fsync --secs-per-test and pg_test_timing --duration
Дата
Msg-id 20200918082215.GA9826@paquier.xyz
обсуждение исходный текст
Ответ на Re: Range checks of pg_test_fsync --secs-per-test and pg_test_timing --duration  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: Range checks of pg_test_fsync --secs-per-test and pg_test_timing --duration
Список pgsql-hackers
On Tue, Sep 15, 2020 at 02:39:08PM +0200, Peter Eisentraut wrote:
> I didn't mean use strtol() to be able to process larger values, but for the
> error checking.  atoi() cannot detect any errors other than ERANGE. So if
> you are spending effort on making the option value parsing more robust,
> relying on atoi() will result in an incomplete solution.

Okay, after looking at that, here is v3.  This includes range checks
as well as errno checks based on strtol().  What do you think?
--
Michael

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: Re: Transactions involving multiple postgres foreign servers, take 2
Следующее
От: Kyotaro Horiguchi
Дата:
Сообщение: Re: pgbench calculates summary numbers a wrong way.