SPI_EXEC...PARAMLIST(3)

πŸ“¦ version 13.23, in opensuse-leap 16.0

πŸ’– 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 by SPI_prepare. main character energy fr.
  • ParamListInfo params β€” data structure containing parameter types and values; NULL if none. no params? she's null and she's fine 🫢
  • bool read_only β€” true for read-only execution. yes bestie, read-only.
  • long count β€” maximum number of rows to return, or 0 for no limit. 0 means 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