Re: pgbench: allow to exit immediately when any client is aborted

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: coelho(at)cri(dot)ensmp(dot)fr
Cc: nagata(at)sraoss(dot)co(dot)jp, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgbench: allow to exit immediately when any client is aborted
Date: 2023-08-17 01:37:58
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> About pgbench exit on abort v4:
> Patch applies cleanly, compiles, local make check ok, doc looks ok.
> This looks ok to me.

I have tested the v4 patch with default_transaction_isolation =
'repeatable read'.

pgbench --exit-on-abort -N -p 11002 -c 10 -T 30 test
pgbench (17devel, server 15.3)
starting vacuum...end.
transaction type: <builtin: simple update>
scaling factor: 1
query mode: simple
number of clients: 10
number of threads: 1
maximum number of tries: 1
duration: 30 s
number of transactions actually processed: 64854
number of failed transactions: 4 (0.006%)
latency average = 4.628 ms (including failures)
initial connection time = 49.526 ms
tps = 2160.827556 (without initial connection time)

Depite the 4 failed transactions (could not serialize access due to
concurrent update) pgbench ran normally, rather than aborting the
test. Is this an expected behavior?

Best reagards,
Tatsuo Ishii

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiro Ikeda 2023-08-17 01:53:02 Re: WIP: new system catalog pg_wait_event
Previous Message Michael Paquier 2023-08-17 01:15:35 Re: pg_logical_emit_message() misses a XLogFlush()