Update EXECUTE docs to mention tag matches prepared statement.

Update log_statement to more clearly state it doesn't filter based on
the statement type of the prepared statement.

diff --git a/doc/src/sgml/ref/execute.sgml b/doc/src/sgml/ref/execute.sgml
index 83c9fa91aaca44bc6227277c5cc63b3af0ab54a1..3e18c061860b45e3aea20763e446d29d5b510dd6 100644 (file)
--- a/doc/src/sgml/ref/execute.sgml
+++ b/doc/src/sgml/ref/execute.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/execute.sgml,v 1.8 2004/01/26 17:26:30 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/execute.sgml,v 1.9 2004/04/22 04:18:41 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -45,6 +45,8 @@ EXECUTE <replaceable class="PARAMETER">plan_name</replaceable> [ (<replaceable c
   </para>
 
   <para>
+   The command tag returned by <command>EXECUTE</command>
+   is that of the prepared statement, and not <literal>EXECUTE</>.
    For more information on the creation and usage of prepared statements,
    see <xref linkend="sql-prepare" endterm="sql-prepare-title">.
   </para>

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 1ec9759c4006d7b3ad4b881a0ee957830ca46a62..d0ed0f35d01a2ed56ff84d38b3e1153fb85edcce 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.261 2004/04/21 13:18:28 petere Exp $
+$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.262 2004/04/22 04:18:37 momjian Exp $
 -->
 
 <Chapter Id="runtime">
@@ -2135,16 +2135,19 @@ SET ENABLE_SEQSCAN TO OFF;
         <literal>UPDATE</>, <literal>DELETE</>, <literal>TRUNCATE</>,
         and <literal>COPY FROM</>. <literal>PREPARE</> and
         <literal>EXPLAIN ANALYZE</> statements are also considered for
-        appropriate commands. The default is <literal>none</>. Only
-        superusers can reduce the detail of this option if it has been
-        set by an administrator.
+        appropriate commands. 
+       </para>
+       <para>
+        The default is <literal>none</>. Only superusers can reduce 
+        the detail of this option if it has been set by an administrator.
        </para>
 
        <note>
         <para>
-         When the <command>EXECUTE</command> statement is logged, only
-         the name of the prepared statement is recorded, not the
-         entire prepared statement.
+         The <command>EXECUTE</command> statement not considered a
+         <literal>ddl</> or <literal>mod</> statement.  When it is logged, 
+         only the name of the prepared statement is reported, not the
+         actual prepared statement.
         </para>
 
         <para>