SPI_EXEC(3)

💖 SPI_EXEC(3) 💖

okay bestie, welcome to the PostgreSQL 18.6 docs, section 3 of the manual, and today's main character is SPI_exec 🎀 no cap, she's a tiny little function with a whole lot of power.

---

✨ NAME ✨

SPI_exec — execute a read/write command 🔥

like literally. she runs your command and she is not here for the read-only lifestyle.

---

✨ SYNOPSIS ✨

int SPI_exec(const char * command, long count)

two args, one int coming back at you. that's the whole vibe 🦋

---

✨ DESCRIPTION ✨

so here's the tea ☕ SPI_exec is literally the same as SPI_execute, except that SPI_execute's read_only parameter is always taken as false. always always. no negotiating, no "but what if", it's just false periodt 💅

which lowkey means: this one is the read/write girlie. she will absolutely let you change things. she said "not me being the dangerous twin" and honestly? iconic.

---

✨ ARGUMENTS ✨

• const char * command — the string containing the command to execute 🍓 like, the actual thing you want her to run, as a string, that's it.
• long count — the maximum number of rows to return, or 0 for no limit 🌈 so if you want everything, you say 0, and she's like "say less".

---

✨ RETURN VALUE ✨

see SPI_execute 👑 she doesn't do her own return value lore, she just points you at her sister's page. iykyk.

---

🫶 quick reminder bestie: read_only is hardwired to false here, so do NOT come crying to me if you wanted a cute little read-only moment. that's not this function. that's SPI_execute. 💀

---

and that's the whole page, you ate it 💖

PostgreSQL 18.6 documentation, dated 2026 — that's the source, the version and the date, mwah, bye bestie, go run some commands responsibly 🧚✨💜