database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-22 23:02:54 +03:00
Code

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 a1c935d3b7
commit d797bf7da2
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

@ -1149,10 +1149,9 @@ END;
Field <replaceable>schedule_lag</> is the difference between the Field <replaceable>schedule_lag</> is the difference between the
transaction's scheduled start time, and the time it actually started, in transaction's scheduled start time, and the time it actually started, in
microseconds. It is only present when the <option>--rate</> option is used. microseconds. It is only present when the <option>--rate</> option is used.
The last field <replaceable>skipped_transactions</> reports the number of When both <option>--rate</> and <option>--latency-limit</> are used,
transactions skipped because they were too far behind schedule. It is only the <replaceable>time</> for a skipped transaction will be reported as
present when both options <option>--rate</> and <option>--latency-limit</> <literal>skipped</>.
are used.
</para> </para>
<para> <para>