SPI_EXEC...PARAMLIST(3)

✨ NAME ✨

Okay bestie, this is SPI_EXEC...PARAMLIST(3) — straight from the PostgreSQL 17.11 Documentation, and it's giving “execute a statement prepared by SPI_prepare” energy. 💅

SPI_execute_plan_with_paramlist — execute a statement prepared by SPI_prepare. Periodt.

---

🌸 SYNOPSIS 🌸

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

---

🦋 DESCRIPTION 🦋

So SPI_execute_plan_with_paramlist executes a statement prepared by SPI_prepare. Literally that's the main character move. 💖

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. No cap. 🫶

⚠️ Heads up, bestie: this function is now deprecated in favor of SPI_execute_plan_extended. So it's still here, but it's lowkey in its legacy era. 💀

---

🎀 ARGUMENTS 🎀

• SPIPlanPtr plan — the prepared statement, returned by SPI_prepare. Your main character plan. 👑
• ParamListInfo params — data structure containing parameter types and values; NULL if none. So if there are no params, pass NULL, simple as that. ✨
• bool read_only — true for read-only execution. Keep it wholesome if you're just reading. 🌸
• long count — maximum number of rows to return, or 0 for no limit. Zero means “give me all the rows, bestie.” 🔥

---

🌈 RETURN VALUE 🌈

The return value is the same as for SPI_execute_plan. Matching energy, matching result. 💜

SPI_processed and SPI_tuptable are set as in SPI_execute_plan if successful. So if it slays and succeeds, those get set the same way. 🎀

---

With love, sparkle, and PostgreSQL 17.11 documentation vibes — dated 2026, bestie. 💖✨🎀🦋