SPI_EXEC...PARAMLIST(3)
π SPI_execute_plan_with_paramlist β the SPI_EXEC...PARAMLIST(3) page, bestie
πΈ NAME πΈ
SPI_execute_plan_with_paramlist β execute a statement prepared by SPI_prepare. Slay.
β¨ SYNOPSIS β¨
int SPI_execute_plan_with_paramlist(SPIPlanPtr plan,
ParamListInfo params,
bool read_only,
long count)
π DESCRIPTION π
okay so SPI_execute_plan_with_paramlist executes a statement prepared by SPI_prepare. This function is equivalent to SPI_execute_plan except that information about the parameter values to be passed to the query is presented differently. The ParamListInfo representation can be convenient for passing down values that are already available in that format. It also supports use of dynamic parameter sets via hook functions specified in ParamListInfo. iykyk π
π ARGUMENTS π
SPIPlanPtr planβ the prepared statement, returned bySPI_prepare. main character energy fr.ParamListInfo paramsβ data structure containing parameter types and values;NULLif none. no params? she's null and she's fine π«Άbool read_onlyβtruefor read-only execution. yes bestie, read-only.long countβ maximum number of rows to return, or0for no limit.0means no cap, periodt.
π RETURN VALUE π
The return value is the same as for SPI_execute_plan. literally same vibe.
SPI_processed and SPI_tuptable are set as in SPI_execute_plan if successful. β¨
π«Ά thatβs the whole page, bestie. source/version/date check: PostgreSQL 13.23, 2025 β the SPI_EXEC...PARAMLIST(3) manual page, and we ate. π
π¦ where this page comes from
- opensuse-leap 16.0: postgresql13-docs 13.23-160000.1.1 Β· PostgreSQL
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms