SPI_FINISH(3)

💖 SPI_FINISH(3) 💖

okay bestie, gather round — this is the PostgreSQL 18.6 manual page for SPI_finish, and it's literally the "okay bye, love u" of the SPI world 🫶

---

✨ NAME ✨

SPI_finish — disconnect a C function from the SPI manager 💅

---

✨ SYNOPSIS ✨

int SPI_finish(void)

---

✨ DESCRIPTION ✨

SPI_finish closes an existing connection to the SPI manager. Think of it as hanging up the phone — you opened the line, you did your little chat, now you gotta end the call, bestie 📞💀

You must call this function after you finish all the SPI operations you needed during your C function's current invocation. No leaving it on read. No ghosting the SPI manager. It's giving rude and it's giving broken. 🙈

BUT — and this is the good part — you do not need to worry about making that happen if you abort the transaction via elog(ERROR). In that case SPI will clean itself up automatically. Self-care king behavior, honestly. ✨🧚

fr fr: normal exit → you call SPI_finish. Error abort via elog(ERROR) → SPI handles it itself, you don't gotta do a thing. 🌸

---

✨ RETURN VALUE ✨

• SPI_OK_FINISH — if properly disconnected 🎀 (the slay outcome, the one you want)
• SPI_ERROR_UNCONNECTED — if called from an unconnected C function 😭 (you tried to hang up a phone that was never picked up)

---

and that's the whole page, no cap. every option, every return value, every vibe — accounted for. periodt. 👑

signing off from the PostgreSQL 18.6 docs, dated 2026 — same manual, same facts, just with infinitely more main character energy 💖✨🎀🦋