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 @@
 
 
@@ -45,6 +45,8 @@ EXECUTE plan_name [ (
   
 
   
+   The command tag returned by EXECUTE
+   is that of the prepared statement, and not EXECUTE.
    For more information on the creation and usage of prepared statements,
    see .
   

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 @@
 
 
 
@@ -2135,16 +2135,19 @@ SET ENABLE_SEQSCAN TO OFF;
         UPDATE, DELETE, TRUNCATE,
         and COPY FROM. PREPARE and
         EXPLAIN ANALYZE statements are also considered for
-        appropriate commands. The default is none. Only
-        superusers can reduce the detail of this option if it has been
-        set by an administrator.
+        appropriate commands. 
+       
+       
+        The default is none. Only superusers can reduce 
+        the detail of this option if it has been set by an administrator.
        
 
        
         
-         When the EXECUTE statement is logged, only
-         the name of the prepared statement is recorded, not the
-         entire prepared statement.
+         The EXECUTE statement not considered a
+         ddl or mod statement.  When it is logged, 
+         only the name of the prepared statement is reported, not the
+         actual prepared statement.