SPI_FINISH(3)

✨ SPI_FINISH(3) ✨

okay so bestie, welcome to the SPI_FINISH(3) page 💅 this one lives in the PostgreSQL 17.11 Documentation and it's all about politely hanging up on the SPI manager 🎀

---

🌸 NAME 🌸

SPI_finish — disconnect a C function from the SPI manager 🫶

---

✨ SYNOPSIS ✨

int SPI_finish(void)

literally that's it, no arguments, iconic behavior 💖

---

🦋 DESCRIPTION 🦋

okay so SPI_finish closes an existing connection to the SPI manager 🌈 think of it as the "bye bestie 👋" you owe the SPI manager when you're done.

You must call this function after completing the SPI operations needed during your C function's current invocation 🔥 like, no cap, it's required.

But don't stress — you do not need to worry about making this happen if you abort the transaction via elog(ERROR) 😌 because in that case SPI will clean itself up automatically ✨ the way it just handles things on its own, main character energy honestly 👑

---

💜 RETURN VALUE 💜

• SPI_OK_FINISH — if properly disconnected 🎀 everything's slaying, connection closed correctly
• SPI_ERROR_UNCONNECTED — if called from an unconnected C function 💀 like bestie you were never connected in the first place, awkward

---

🌸 quick vibe check: that's the whole page — every option, every return value, every detail, all here 💅 no skips, no cuts, periodt.

---

✨ that's a wrap, bestie ✨ this page is from PostgreSQL 17.11, dated 2026, and it's SPI_FINISH(3) 🦋 go forth and disconnect responsibly 💖🎀👑