Mention that log_statement only prints query on PREPARE, not EXECUTE,

and PL/pgSQL only prints queries on first function call.

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index ad4a6f98456f5f1fab34def3ce18c7127c67b3e5..db9a8268d7c899d4d6b9b763ee55d3dfb353ed58 100644 (file)
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.232 2004/01/23 23:54:20 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.233 2004/01/25 00:36:18 momjian Exp $
 -->
 
 <Chapter Id="runtime">
@@ -1822,8 +1822,11 @@ SET ENABLE_SEQSCAN TO OFF;
       <listitem>
        <para>
         Causes each SQL statement to be logged. The default is off.
-        Only superusers can turn off this option if it is enabled by
-        the administrator.
+        <command>EXECUTE</> only displays the plan name, not the
+        prepared query. Server-side languages like
+        <application>PL/pgSQL</> that store functions in a cache only
+        display their queries on first function call. superusers can
+        turn off this option if it is enabled by the administrator.
        </para>
       </listitem>
      </varlistentry>