SPI_EXEC...PARAMLIST(3)

💅 SPI_EXEC...PARAMLIST(3) 💅

okay so bestie, welcome to the PostgreSQL 16.15 Documentation page for SPI_EXEC...PARAMLIST(3) — this is the one about executing a statement that was prepared by SPI_prepare. pull up a chair, we're getting into it 🫶

---

✨ NAME ✨

SPI_execute_plan_with_paramlist — execute a statement prepared by SPI_prepare

---

🦋 SYNOPSIS 🦋

int SPI_execute_plan_with_paramlist(SPIPlanPtr plan,
                                    ParamListInfo params,
                                    bool read_only,
                                    long count)

---

🌸 DESCRIPTION 🌸

SPI_execute_plan_with_paramlist executes a statement prepared by SPI_prepare. no cap, that's the whole main-character job 💅

This function is equivalent to SPI_execute_plan except that information about the parameter values to be passed to the query is presented differently. it's giving "same task, different outfit" ✨ 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.

⚠️ deprecated alert: this function is now deprecated in favor of SPI_execute_plan_extended. bestie, use the newer one when you can — iykyk 😭

---

🎀 ARGUMENTS 🎀

• SPIPlanPtr plan — prepared statement (returned by SPI_prepare) 🧚
• ParamListInfo params — data structure containing parameter types and values; NULL if none
• bool read_only — true for read-only execution
• long count — maximum number of rows to return, or 0 for no limit

---

🌈 RETURN VALUE 🌈

The return value is the same as for SPI_execute_plan. periodt 💖

SPI_processed and SPI_tuptable are set as in SPI_execute_plan if successful. so if it slays, those get set the same way — literally no extra lore there 🔥

---

mwah 💋 and that's the page, bestie — source/version is PostgreSQL 16.15, dated 2026, and the page is SPI_EXEC...PARAMLIST(3) 🎀✨