pgsql: Allow pgbench to exit immediately when any client is aborted.

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Allow pgbench to exit immediately when any client is aborted.
Date: 2023-08-30 01:05:15
Message-ID: E1qb9dy-001bO7-NI@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Allow pgbench to exit immediately when any client is aborted.

Previously when client was aborted due to some error during
benchmarking, other clients continued their run until certain number
of transactions specified -t was reached or the time specified by -T
was expired. At the end, the results are printed with caution: "Run
was aborted; the above results are incomplete" shows.

New option "--exit-on-abort" allows pgbench to exit immediately in
this case so that users could quickly fix the cause of the failure and
try again another round of benchmarking.

Author: Yugo Nagata
Reviewed-by: Fabien COELHO, Tatsuo Ishii
Discussion: https://postgr.es/m/flat/20230804130325.df32e60879c38c92bca64207%40sraoss.co.jp

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/3c662643c4bb94aaf384e83fcfb53f6e4da0035e

Modified Files
--------------
doc/src/sgml/ref/pgbench.sgml | 28 ++++++++++++++++++++---
src/bin/pgbench/pgbench.c | 33 +++++++++++++++++++++++++++-
src/bin/pgbench/t/001_pgbench_with_server.pl | 26 ++++++++++++++++++++++
3 files changed, 83 insertions(+), 4 deletions(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2023-08-30 01:33:39 pgsql: Fix misuse of PqMsg_Close.
Previous Message Michael Paquier 2023-08-29 23:33:49 pgsql: Fix comment of PQputCopyEnd()