1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
HREF="mailto:pgsql-docs@postgresql.org"><LINK
12
TITLE="PostgreSQL 9.3beta1 Documentation"
13
HREF="index.html"><LINK
15
TITLE="Interface Functions"
16
HREF="spi-interface.html"><LINK
19
HREF="spi-spi-keepplan.html"><LINK
21
TITLE="Interface Support Functions"
22
HREF="spi-interface-support.html"><LINK
25
HREF="stylesheet.css"><META
26
HTTP-EQUIV="Content-Type"
27
CONTENT="text/html; charset=ISO-8859-1"><META
29
CONTENT="2013-05-06T21:00:50"></HEAD
35
SUMMARY="Header navigation table"
47
>PostgreSQL 9.3beta1 Documentation</A
57
HREF="spi-spi-keepplan.html"
66
HREF="spi-interface.html"
80
TITLE="Interface Support Functions"
81
HREF="spi-interface-support.html"
92
NAME="SPI-SPI-SAVEPLAN"
102
>SPI_saveplan -- save a prepared statement</DIV
104
CLASS="REFSYNOPSISDIV"
112
>SPIPlanPtr SPI_saveplan(SPIPlanPtr <TT
128
> copies a passed statement (prepared by
132
>) into memory that will not be freed
136
> nor by the transaction manager,
137
and returns a pointer to the copied statement. This gives you the
138
ability to reuse prepared statements in the subsequent invocations of
139
your procedure in the current session.
164
> the prepared statement to be saved
178
> Pointer to the copied statement; or <TT
195
>SPI_ERROR_ARGUMENT</TT
211
>SPI_ERROR_UNCONNECTED</TT
215
> if called from an unconnected procedure
231
> The originally passed-in statement is not freed, so you might wish to do
235
> on it to avoid leaking memory
242
> In most cases, <CODE
245
> is preferred to this
246
function, since it accomplishes largely the same result without needing
247
to physically copy the prepared statement's data structures.
255
SUMMARY="Footer navigation table"
266
HREF="spi-spi-keepplan.html"
284
HREF="spi-interface-support.html"
300
HREF="spi-interface.html"
308
>Interface Support Functions</TD
b'\\ No newline at end of file'