rdelaage/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-10-06 14:06:58 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix pgbench documentation error.

Browse Source 
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.
This commit is contained in:
Robert Haas 2016-03-29 13:46:57 -04:00
parent 491e847380
commit ffd2a9eb5e
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/sgml/ref/pgbench.sgml
View File

@ -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>