SPI_FREEPLAN(3)

💅 SPI_FREEPLAN(3) — the PostgreSQL 14.24 glow-up edition ✨

okay so bestie, welcome to the manual page for SPI_freeplan, straight out of the PostgreSQL 14.24 Documentation. it's short, it's sweet, and it's literally the cleanup crew of prepared statements 🧹🫶

---

🌸 NAME 🌸

SPI_freeplan — frees a prepared statement that you saved earlier. yes queen, we're doing the responsible thing and cleaning up after ourselves 💖

---

✨ SYNOPSIS ✨

int SPI_freeplan(SPIPlanPtr plan)

one function, one pointer, zero drama. look at her go 🦋

---

🎀 DESCRIPTION 🎀

so here's the tea ☕: SPI_freeplan releases a prepared statement — specifically the kind that was previously returned by SPI_prepare, or saved by SPI_keepplan or SPI_saveplan.

think of it as the "okay bestie, you can go now, thank you for your service" moment 👑 like, you kept that plan around, it did its job, and now it's officially time to set it free. main character exit, no cap ✨

---

💅 ARGUMENTS 💅

• SPIPlanPtr plan — pointer to the statement you want to free. that's it, that's the whole arg. give her the pointer and she'll handle the rest 🫶

---

🌈 RETURN VALUE 🌈

• 0 on success — slay, the plan is freed, we love a clean exit 💖
• SPI_ERROR_ARGUMENT if plan is NULL or invalid — ngl, if you hand her a null or bogus pointer she will hit you with this 💀 so maybe double-check your pointer first, iykyk

---

⭐ SEE ALSO ⭐

(fr fr, the original page didn't list any SEE ALSO refs, so there's nothing extra to link here — just you, your plan pointer, and the freeing thereof 🧚)

---

🫶 reminder bestie: freeing something that's NULL or invalid gets you SPI_ERROR_ARGUMENT, not a crash-and-burn situation — but still, vibe check your pointers before you send them 💅

---

and that's the whole page, bestie 💜 short and iconic, just like the original — which comes to you courtesy of PostgreSQL 14.24, dated 2026. go forth and free your plans responsibly, mwah 😭🎀🌸