postgres.git / summary / log / commit / refs

commit    2472ea0a53f0e3fe7cb315fbbe6619fa71b181f9
Author:   Tatsuo Ishii <ishii@postgresql.org>
Date:     Thu Jan 17 06:34:41 2019 +0000

    Doc: enhance pgbench manual.
    
    Clarify the difference between "prepared mode" and other query modes.
    
    Discussion: https://postgr.es/m/20181030.103654.2249812451112831300.t-ishii@sraoss.co.jp
    Reviewed by: Fabien Coelh and Alvaro Herrera.


 doc/src/sgml/ref/pgbench.sgml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml
index ca160881188..15ee7c0f2ba 100644
--- a/doc/src/sgml/ref/pgbench.sgml
+++ b/doc/src/sgml/ref/pgbench.sgml
@@ -473,6 +473,13 @@ pgbench <optional> <replaceable>options</replaceable> </optional> <replaceable>d
             <para><literal>prepared</literal>: use extended query protocol with prepared statements.</para>
            </listitem>
           </itemizedlist>
+
+        Because in "prepared" mode <application>pgbench</application> reuses
+        the parse analysis result for the second and subsequent query
+        iteration, <application>pgbench</application> runs faster in the
+        prepared mode than in other modes.
+       </para>
+       <para>
         The default is simple query protocol.  (See <xref linkend="protocol"/>
         for more information.)
        </para>


[parent: 6c61d7c59357]