From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> |
Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, kuroda(dot)hayato(at)fujitsu(dot)com, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pgbench bug candidate: negative "initial connection time" |
Date: | 2021-09-24 02:26:12 |
Message-ID: | 71ba41e8-017a-8bd9-e16e-7edb337e422d@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2021/09/24 7:26, Yugo NAGATA wrote:
> That makes sense. Failures of setup connection or initial connection doesn't
> seem 'static problems'. I rewrote this description to explain exit status 1
> indicates also interal errors and early errors.
>
> Exit status 1 indicates static problems such as invalid command-line options
> or internal errors which are supposed to never occur. Early errors that occur
> when starting benchmark such as initial connection failures also exit with
> status 1.
LGTM. Barring any objection, I will commit the patch.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2021-09-24 02:32:57 | Re: prevent immature WAL streaming |
Previous Message | Daniel Fone | 2021-09-24 02:12:08 | pgcrypto support for bcrypt $2b$ hashes |