From 825da2aba8ae7a5824e9fb3823125c5c755ea568 Mon Sep 17 00:00:00 2001 From: Noah Misch Date: Mon, 23 Sep 2013 15:49:21 -0400 Subject: [PATCH] pgbench: Tweak documentation. Fabien COELHO --- contrib/pgbench/pgbench.c | 2 +- doc/src/sgml/pgbench.sgml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/contrib/pgbench/pgbench.c b/contrib/pgbench/pgbench.c index ad8e272c91..06dd7093fa 100644 --- a/contrib/pgbench/pgbench.c +++ b/contrib/pgbench/pgbench.c @@ -369,7 +369,7 @@ usage(void) " -N, --skip-some-updates skip updates of pgbench_tellers and pgbench_branches\n" " -P, --progress=NUM show thread progress report every NUM seconds\n" " -r, --report-latencies report average latency per command\n" - " -R, --rate=SPEC target rate in transactions per second\n" + " -R, --rate=NUM target rate in transactions per second\n" " -s, --scale=NUM report this scale factor in output\n" " -S, --select-only perform SELECT-only transactions\n" " -t, --transactions number of transactions each client runs " diff --git a/doc/src/sgml/pgbench.sgml b/doc/src/sgml/pgbench.sgml index 49a79b194e..5871b459e7 100644 --- a/doc/src/sgml/pgbench.sgml +++ b/doc/src/sgml/pgbench.sgml @@ -429,7 +429,7 @@ pgbench options dbname The rate is targeted by starting transactions along a - Poisson-distributed schedule time line. The expected finish time + Poisson-distributed schedule time line. The expected start time schedule moves forward based on when the client first started, not when the previous transaction ended. That approach means that when transactions go past their original scheduled end time, it is