aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2016-03-29 13:46:57 -0400
committerRobert Haas <rhaas@postgresql.org>2016-03-29 13:53:51 -0400
commitffd2a9eb5ede1340bd949c032ed8b7ef92b3ca09 (patch)
treeff0c7b8110ce87c8f6baf6c28efc90b0bd4e9d6b /doc/src
parent491e847380740dac54d4ecae820261bbaa8aee44 (diff)
downloadpostgresql-ffd2a9eb5ede1340bd949c032ed8b7ef92b3ca09.tar.gz
postgresql-ffd2a9eb5ede1340bd949c032ed8b7ef92b3ca09.zip
Fix pgbench documentation error.
The description of what the per-transaction log file says for skipped transactions is just plain wrong. Report and patch by Tomas Vondra, reviewed by Fabien Coelho and modified by me.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/ref/pgbench.sgml7
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml
index aafb18d6536..a70c8cf3a2d 100644
--- a/doc/src/sgml/ref/pgbench.sgml
+++ b/doc/src/sgml/ref/pgbench.sgml
@@ -993,10 +993,9 @@ END;
Field <replaceable>schedule_lag</> is the difference between the
transaction's scheduled start time, and the time it actually started, in
microseconds. It is only present when the <option>--rate</> option is used.
- The last field <replaceable>skipped_transactions</> reports the number of
- transactions skipped because they were too far behind schedule. It is only
- present when both options <option>--rate</> and <option>--latency-limit</>
- are used.
+ When both <option>--rate</> and <option>--latency-limit</> are used,
+ the <replaceable>time</> for a skipped transaction will be reported as
+ <literal>skipped</>.
</para>
<para>