SPI_saveplan copies a passed
statement (prepared by
into memory that will not be freed by
SPI_finish nor by the transaction manager, and
returns a pointer to the copied statement. This gives you the
ability to reuse prepared statements in the subsequent
invocations of your procedure in the current session.
Pointer to the copied statement; or NULL if unsuccessful. On error, SPI_result is set thus:
if plan is NULL or invalid
if called from an unconnected procedure
The originally passed-in statement is not freed, so you might
wish to do
SPI_freeplan on it to
avoid leaking memory until
In most cases,
preferred to this function, since it accomplishes largely the
same result without needing to physically copy the prepared
statement's data structures.
Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.
Proceed to the comment form.