SPI_EXECP(3)

✨ SPI_EXECP(3) ✨

okay so bestie, welcome to the tea on SPI_EXECP(3) — it's a page from the PostgreSQL 14.24 Documentation and honestly it's giving "short but mighty" 💅

---

🌸 NAME 🌸

SPI_execp — execute a statement in read/write mode 🔥

---

🎀 SYNOPSIS 🎀

int SPI_execp(SPIPlanPtr plan, Datum * values, const char * nulls, long count)

---

🦋 DESCRIPTION 🦋

okay so SPI_execp is literally the same as SPI_execute_plan, except that the read_only parameter of that other function is always taken as false. periodt. that's the whole vibe — you're in read/write mode, no cap 💀

---

💖 ARGUMENTS 💖

• SPIPlanPtr plan — the prepared statement, which you get back from SPI_prepare 🫶
• Datum * values — an array of the actual parameter values you're passing in. it has to have the same length as the statement's number of arguments, fr fr.
• const char * nulls — an array that describes which parameters are null. also has to have the same length as the statement's number of arguments ✨

if nulls is NULL, then SPI_execp assumes that no parameters are null. otherwise, each entry of the nulls array should be ' ' if the corresponding parameter value is non-null, or 'n' if the corresponding parameter value is null. (and in that null case? the actual value in the corresponding values entry doesn't matter, so don't stress 🙈)

heads up bestie: nulls is not a text string, it's just an array — so it does not need a '\0' terminator. it's giving "array not string" energy, iykyk ⭐

• long count — maximum number of rows to return, or 0 for no limit 👑

---

🌈 RETURN VALUE 🌈

see SPI_execute_plan — that's where the return value tea lives 💜

SPI_processed and SPI_tuptable are set as in SPI_execute if successful ✨

---

and that's the whole page, bestie — short, sweet, and iconic 🎀 sign-off time: this one's from PostgreSQL 14.24, dated 2026 — slay 💅