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

Поиск
Список
Период
Сортировка
От Tatsuo Ishii
Тема Re: pgbench: allow to exit immediately when any client is aborted
Дата
Msg-id 20230817.103758.571754322794167574.t-ishii@sranhm.sra.co.jp
обсуждение исходный текст
Ответ на Re: pgbench: allow to exit immediately when any client is aborted  (Fabien COELHO <coelho@cri.ensmp.fr>)
Ответы Re: pgbench: allow to exit immediately when any client is aborted  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Список 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
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: pg_logical_emit_message() misses a XLogFlush()
Следующее
От: Masahiro Ikeda
Дата:
Сообщение: Re: WIP: new system catalog pg_wait_event