SPI_KEEPPLAN(3)

💅 SPI_KEEPPLAN(3) 💅

okay so this is the SPI_KEEPPLAN(3) page from the PostgreSQL 14.24 Documentation, and it’s lowkey iconic for anyone writing C functions that need a prepared statement to stay put across calls. bestie, this is the “don’t free my plan” button 🫶✨

✨ NAME ✨

SPI_keepplan — save a prepared statement, periodt 💾💖

🦋 SYNOPSIS 🦋

int SPI_keepplan(SPIPlanPtr plan)

🌸 DESCRIPTION 🌸

SPI_keepplan saves a passed statement — one that was prepared by SPI_prepare — so that it will not be freed by SPI_finish nor by the transaction manager. no cap, that’s the whole vibe 🔥

This gives you the ability to reuse prepared statements in the subsequent invocations of your C function in the current session. literally the “keep it for later” main character move 👑💫

🎀 ARGUMENTS 🎀

• SPIPlanPtr plan — the prepared statement to be saved 💖

⭐ RETURN VALUE ⭐

• 0 on success 🎉
• SPI_ERROR_ARGUMENT if plan is NULL or invalid 😭

💜 NOTES 💜

The passed-in statement is relocated to permanent storage by means of pointer adjustment — and ngl, no data copying is required 🧚✨. If you later wish to delete it, use SPI_freeplan on it. that’s the cleanup era 💅

big mwah 💋 — this one’s from PostgreSQL 14.24, dated 2026, and it’s the SPI_KEEPPLAN(3) page, periodt 🌈🫶