From 2399651ef9587242e7e4682608e1e270ce0ba7a6 Mon Sep 17 00:00:00 2001 From: "Chao Li (Evan)" Date: Thu, 18 Jun 2026 14:21:13 +0800 Subject: [PATCH v3] doc: Clarify pgbench reporting with --continue-on-error Clarify that transactions failed under --continue-on-error are reported separately and are not counted as transactions actually processed or in TPS. Also adjust the latency description to avoid implying that failed transactions are generally included in latency measurements. Author: Chao Li Author: Fujii Masao Reviewed-by: Yugo Nagata Reviewed-by: Fujii Masao Reviewed-by: Xuneng Zhou Discussion: https://postgr.es/m/597C9755-4386-488D-A289-16D50AD81FBF@gmail.com --- doc/src/sgml/ref/pgbench.sgml | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml index 2e401d1ceb8..9688527c955 100644 --- a/doc/src/sgml/ref/pgbench.sgml +++ b/doc/src/sgml/ref/pgbench.sgml @@ -770,10 +770,15 @@ pgbench options d the connection to fail. See for more information. + This option is useful when your custom script may raise errors such as unique constraint violations, but you want the benchmark - to continue and measure performance including those failures. + to continue despite individual statement failures. Failed + transactions are reported separately, but are not counted as + transactions actually processed; time spent on failed transactions + remains part of the benchmark duration, so such failures can lower + the reported TPS. @@ -2933,9 +2938,17 @@ statement latencies in milliseconds, failures and retries: The latency of a successful transaction includes the entire time of - transaction execution with rollbacks and retries. The latency is measured - only for successful transactions and commands but not for failed transactions - or commands. + transaction execution with rollbacks and retries. In the main report, + when neither , , nor + is specified, the + latency average is computed from the total benchmark + duration divided by both successful and failed transactions, and therefore + includes failed transactions. Otherwise, the latency + average and latency stddev shown in the main + report are measured only for successful transactions. Detailed latency + statistics, including the per-script and per-command reports, are also + measured only for successful transactions and commands, not for failed + transactions or commands. -- 2.50.1 (Apple Git-155)