From 8303a3d1eaba04d470d5a7c0cfc46cbd13d7f8fd Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sun, 25 Jan 2004 00:36:18 +0000
Subject: [PATCH] Mention that log_statement only prints query on PREPARE, not
EXECUTE, and PL/pgSQL only prints queries on first function call.
---
doc/src/sgml/runtime.sgml | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index ad4a6f98456..db9a8268d7c 100644
--- 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>
--
GitLab