Skip to content

Commit d1b3915

Browse files
committed
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 parent 011c3e6 commit d1b3915

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

doc/src/sgml/ref/prepare.sgml

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/prepare.sgml,v 1.11 2004/01/26 17:26:31 neilc Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/prepare.sgml,v 1.12 2004/04/19 23:36:48 momjian Exp $
33
PostgreSQL documentation
44
-->
55

@@ -54,10 +54,11 @@ PREPARE <replaceable class="PARAMETER">plan_name</replaceable> [ (<replaceable c
5454
<para>
5555
Prepared statements only last for the duration of the current
5656
database session. When the session ends, the prepared statement is
57-
forgotten, so it must be recreated before being used again. This
58-
also means that a single prepared statement cannot be used by
59-
multiple simultaneous database clients; however, each client can
60-
create their own prepared statement to use.
57+
forgotten, so it must be recreated before being used again. This
58+
also means that a single prepared statement cannot be used by
59+
multiple simultaneous database clients; however, each client can create
60+
their own prepared statement to use. The prepared statement can be
61+
manually cleaned up using the <command>DEALLOCATE</> command.
6162
</para>
6263

6364
<para>

0 commit comments

Comments
 (0)