Query: spi_saveplan
OS: centos
Section: 3
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
SPI_SAVEPLAN(3) PostgreSQL 9.2.7 Documentation SPI_SAVEPLAN(3)NAMESPI_saveplan - save a prepared statementSYNOPSISSPIPlanPtr SPI_saveplan(SPIPlanPtr plan)DESCRIPTIONSPI_saveplan copies a passed statement (prepared by SPI_prepare) 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.ARGUMENTSSPIPlanPtr plan the prepared statement to be savedRETURN VALUEPointer to the copied statement; or NULL if unsuccessful. On error, SPI_result is set thus: SPI_ERROR_ARGUMENT if plan is NULL or invalid SPI_ERROR_UNCONNECTED if called from an unconnected procedureNOTESThe originally passed-in statement is not freed, so you might wish to do SPI_freeplan on it to avoid leaking memory until SPI_finish. In most cases, SPI_keepplan is preferred to this function, since it accomplishes largely the same result without needing to physically copy the prepared statement's data structures. PostgreSQL 9.2.7 2014-02-17 SPI_SAVEPLAN(3)
Related Man Pages |
---|
execute(7) - centos |
spi_cursor_open(3) - centos |
spi_execute_plan(3) - centos |
execute(7) - mojave |
prepare(7) - osx |
Similar Topics in the Unix Linux Community |
---|
Set hard block limit for user using quota |
CentOS7 restoring file capabilities |
Docker learning Phase-I |
CentOS 6 ran out of space, need to reclaim it |
Controlling user input |