diff options
| author | Robert Haas <rhaas@postgresql.org> | 2016-03-29 13:46:57 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2016-03-29 13:50:10 -0400 |
| commit | d797bf7da2cc954f7b5cd2776b65c6e91cd0cb04 (patch) | |
| tree | d7fff175477242eef5e7552e5aa3846429130ef2 | |
| parent | a1c935d3b71e44ba36530d47c3ccab6cc9b9eafe (diff) | |
| download | postgresql-d797bf7da2cc954f7b5cd2776b65c6e91cd0cb04.tar.gz postgresql-d797bf7da2cc954f7b5cd2776b65c6e91cd0cb04.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.
| -rw-r--r-- | doc/src/sgml/ref/pgbench.sgml | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml index 1d13897030d..9707c30c2eb 100644 --- a/doc/src/sgml/ref/pgbench.sgml +++ b/doc/src/sgml/ref/pgbench.sgml @@ -1149,10 +1149,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> |