SPI_freetuptable frees a row set
created by a prior SPI command execution function, such as
SPI_execute. Therefore, this
function is often called with the global variable SPI_tuptable as argument.
This function is useful if a SPI procedure needs to execute
multiple commands and does not want to keep the results of
earlier commands around until it ends. Note that any unfreed row
sets will be freed anyway at
SPI_finish. Also, if a subtransaction is
started and then aborted within execution of a SPI procedure, SPI
automatically frees any row sets created while the subtransaction
Beginning in PostgreSQL 9.3,
SPI_freetuptable contains guard
logic to protect against duplicate deletion requests for the same
row set. In previous releases, duplicate deletions would lead to
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.