aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTatsuo Ishii <ishii@postgresql.org>2019-01-17 15:34:41 +0900
committerTatsuo Ishii <ishii@postgresql.org>2019-01-17 15:34:41 +0900
commit2472ea0a53f0e3fe7cb315fbbe6619fa71b181f9 (patch)
treeca392d1f94d5a12f3018c48c9ff05efe2213aee7
parent6c61d7c5935793e218d2335ac540a2cea7eacdce (diff)
downloadpostgresql-2472ea0a53f0e3fe7cb315fbbe6619fa71b181f9.tar.gz
postgresql-2472ea0a53f0e3fe7cb315fbbe6619fa71b181f9.zip
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.
-rw-r--r--doc/src/sgml/ref/pgbench.sgml7
1 files changed, 7 insertions, 0 deletions
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>