SPI_SAVEPLAN(3)

💅 SPI_SAVEPLAN 💅

okay bestie, so this is a page from the PostgreSQL 17.11 Documentation set, and it's literally all about SPI_saveplan — a function that saves a prepared statement so it doesn't ghost you when the transaction ends. no cap, it's lowkey iconic for anyone writing C functions that need to reuse a plan across calls. 🫶

---

✨ NAME ✨

SPI_saveplan — save a prepared statement 💾

---

🎀 SYNOPSIS 🎀

SPIPlanPtr SPI_saveplan(SPIPlanPtr plan)

---

🌸 DESCRIPTION 🌸

so SPI_saveplan copies a statement you pass in (one that was prepared by SPI_prepare, mmkay) into memory that will not be freed by SPI_finish nor by the transaction manager — and then it hands you back a pointer to that copied statement. the way this works is it literally gives you the ability to reuse prepared statements in the subsequent invocations of your C function in the current session. main character energy fr fr. ✨

---

🦋 ARGUMENTS 🦋

• SPIPlanPtr plan — the prepared statement that's getting saved, bestie. that's the one. 🎀

---

💜 RETURN VALUE 💜

you get back a pointer to the copied statement 💖 … or NULL if it didn't work out 😭. on error, SPI_result gets set like this:

• SPI_ERROR_ARGUMENT — happens if plan is NULL or invalid. yeah. not great. 💀
• SPI_ERROR_UNCONNECTED — happens if it's called from an unconnected C function. 🙈

---

⭐ NOTES ⭐

the originally passed-in statement is not freed, so you might want to do SPI_freeplan on it to avoid leaking memory until SPI_finish. don't forget, okay? your memory will thank you. 🧚

in most cases, SPI_keepplan is preferred to this function, since it accomplishes largely the same result without needing to physically copy the prepared statement's data structures. so like… consider it? 👀

---

and that's the whole vibe check, bestie 💅 this page came to you courtesy of PostgreSQL 17.11, dated 2026 — go forth and save those plans responsibly 🍓👑🌈