RE: pgbench bug candidate: negative "initial connection time"

Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>

From: "kuroda.hayato@fujitsu.com" <kuroda.hayato@fujitsu.com>

To: 'Fabien COELHO' <coelho@cri.ensmp.fr>

Cc: "'pgsql-hackers@lists.postgresql.org'" <pgsql-hackers@lists.postgresql.org>

Date: 2021-06-14T00:42:12Z

Lists: pgsql-hackers

Dear Fabien,

Thank you for replying!

> Hmmm. Possibly. Another option could be not to report anything after some 
> errors. I'm not sure, because it would depend on the use case. I guess the 
> command returned an error status as well.

I did not know any use cases and decisions , but I vote to report nothing when error occurs.

Best Regards,
Hayato Kuroda
FUJITSU LIMITED

Commits

pgbench: Fix typo in comment.
- d8dba4d03068 15.0 landed
pgbench: Improve error-handling in pgbench.
- cd29be5459f0 15.0 landed
pgbench: Fix handling of socket errors during benchmark.
- c5f7e702d78f 12.9 landed
- 8cf4f7118596 13.5 landed
- 8231c500ed74 14.1 landed
- 2acb7cc6b56c 15.0 landed
pgbench: Correct log level of message output when socket wait method fails.
- 3cc85d7d5353 13.5 landed
- 8021334d3710 14.1 landed
- d33674708948 15.0 landed
pgbench: Synchronize client threads.
- aeb57af8e640 14.0 cited
pgbench: Use common logging API
- 30a3e772b401 13.0 cited