In reading the 7.4.2 docs, the sql reference page for PREPARE doesn't

reference DEALLOCATE in any way. It points to EXECUTE, but not to
DEALLOCATE. Suggested fix:

... This also means that a single  prepared statement cannot be used by
multiple simultaneous database clients; however, each client can create
their own prepared statement  to use. The prepared statement can be
manually cleaned up using the DEALLOCATE command.

James Robinson

1 files changed, 6 insertions, 5 deletions

diff --git a/doc/src/sgml/ref/prepare.sgml b/doc/src/sgml/ref/prepare.sgml
index 780c5231c4b..6a77048c3eb 100644
--- a/doc/src/sgml/ref/prepare.sgml
+++ b/doc/src/sgml/ref/prepare.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/prepare.sgml,v 1.11 2004/01/26 17:26:31 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/prepare.sgml,v 1.12 2004/04/19 23:36:48 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -54,10 +54,11 @@ PREPARE <replaceable class="PARAMETER">plan_name</replaceable> [ (<replaceable c
   <para>
    Prepared statements only last for the duration of the current
    database session. When the session ends, the prepared statement is
-   forgotten, so it must be recreated before being used again. This
-   also means that a single prepared statement cannot be used by
-   multiple simultaneous database clients; however, each client can
-   create their own prepared statement to use.
+   forgotten, so it must be recreated before being used again. This 
+   also means that a single  prepared statement cannot be used by
+   multiple simultaneous database clients; however, each client can create
+   their own prepared statement to use.  The prepared statement can be
+   manually cleaned up using the <command>DEALLOCATE</> command.
   </para>
 
   <para>