pgsql: pgbench: Report errors during run better

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: pgbench: Report errors during run better
Date: 2018-10-15 08:36:27
Message-ID: E1gByMV-0004QG-A1@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

pgbench: Report errors during run better

When an error occurs during a benchmark run, exit with a nonzero exit
code and write a message at the end. Previously, it would just print
the error message when it happened but then proceed to print the run
summary normally and exit with status 0. To still allow
distinguishing setup from run-time errors, we use exit status 2 for
the new state, whereas existing errors during pgbench initialization
use exit status 1.

Reviewed-by: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/5b75a4f8266a4f187a47929fed0582ee778c703f

Modified Files
--------------
doc/src/sgml/ref/pgbench.sgml | 12 ++++++
src/bin/pgbench/pgbench.c | 11 +++++-
src/bin/pgbench/t/001_pgbench_with_server.pl | 57 ++++++++++++++--------------
3 files changed, 51 insertions(+), 29 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2018-10-15 09:40:40 pgsql: Translation updates
Previous Message Peter Eisentraut 2018-10-15 08:08:00 pgsql: Make spelling of "acknowledgment" consistent