agora inbox for pgsql-committers@postgresql.orghelp / color / mirror / Atom feed
pgsql: doc: Clarify pgbench reporting with --continue-on-error 2+ messages / 1 participants [nested] [flat]
* pgsql: doc: Clarify pgbench reporting with --continue-on-error @ 2026-08-13 04:27 Fujii Masao <fujii@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Fujii Masao @ 2026-08-13 04:27 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 <lic@highgo.com> Reviewed-by: Yugo Nagata <nagata@sraoss.co.jp> Reviewed-by: Xuneng Zhou <xunengzhou@gmail.com> Reviewed-by: Fujii Masao <masao.fujii@gmail.com> Discussion: https://postgr.es/m/597C9755-4386-488D-A289-16D50AD81FBF@gmail.com Backpatch-through: 19 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/bcb15f48786df1c4c3c0428645b5b0c6da0f3cb7 Modified Files -------------- doc/src/sgml/ref/pgbench.sgml | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: doc: Clarify pgbench reporting with --continue-on-error @ 2026-08-13 04:28 Fujii Masao <fujii@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Fujii Masao @ 2026-08-13 04:28 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 <lic@highgo.com> Reviewed-by: Yugo Nagata <nagata@sraoss.co.jp> Reviewed-by: Xuneng Zhou <xunengzhou@gmail.com> Reviewed-by: Fujii Masao <masao.fujii@gmail.com> Discussion: https://postgr.es/m/597C9755-4386-488D-A289-16D50AD81FBF@gmail.com 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(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2026-08-13 04:28 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-08-13 04:27 pgsql: doc: Clarify pgbench reporting with --continue-on-error Fujii Masao <fujii@postgresql.org> 2026-08-13 04:28 pgsql: doc: Clarify pgbench reporting with --continue-on-error Fujii Masao <fujii@postgresql.org>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox