postgres.git / summary / log / commit / refs

commit    ffd2a9eb5ede1340bd949c032ed8b7ef92b3ca09
Author:   Robert Haas <rhaas@postgresql.org>
Date:     Tue Mar 29 17:46:57 2016 +0000

    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.


 doc/src/sgml/ref/pgbench.sgml | 7 +++----
 1 file 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>


[parent: 491e84738074]