From e3391133ae15c200ef32e5dd512db9d21a7393b3 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Thu, 22 Apr 2004 04:18:41 +0000
Subject: 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.
---
doc/src/sgml/ref/execute.sgml | 4 +++-
doc/src/sgml/runtime.sgml | 17 ++++++++++-------
2 files changed, 13 insertions(+), 8 deletions(-)
(limited to 'doc/src')
diff --git a/doc/src/sgml/ref/execute.sgml b/doc/src/sgml/ref/execute.sgml
index 83c9fa91aac..3e18c061860 100644
--- 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 1ec9759c400..d0ed0f35d01 100644
--- 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.
--
cgit v1.2.3