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, while time spent on them can lower reported TPS. Also adjust the latency description to avoid implying that failed transactions are generally included in latency measurements.
Backpatch to v19, where pgbench's --continue-on-error option was introduced. Author: Chao Li <[email protected]> Reviewed-by: Yugo Nagata <[email protected]> Reviewed-by: Xuneng Zhou <[email protected]> Reviewed-by: Fujii Masao <[email protected]> Discussion: https://postgr.es/m/[email protected] Backpatch-through: 19 Branch ------ REL_19_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/ed23f7ce7f8f633175ae785d18577fbc440139ae Modified Files -------------- doc/src/sgml/ref/pgbench.sgml | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-)
