SPI_START_TRANSACTION(3)

✨ SPI_START_TRANSACTION(3) ✨

okay bestie, welcome to the PostgreSQL 18.6 Documentation corner of the group chat 🫶 this one's a lil historical artifact, a fossil, a vibe from back in the day. Let's get into it 💅

🎀 NAME 🎀

SPI_start_transaction — the obsolete function 👑 she's retired, she's living her best life doing absolutely nothing, and honestly? iconic.

🌸 SYNOPSIS 🌸

void SPI_start_transaction(void)

🦋 DESCRIPTION 🦋

So here's the tea, bestie ☕ SPI_start_transaction does nothing. Like, literally nothing. Zero. Nada. She is the human equivalent of a read receipt 💀 and she exists for one reason only: code compatibility with earlier PostgreSQL releases. That's it. That's the whole job.

Back in the day — the before times 🕰️ — you had to call her after calling SPI_commit or SPI_rollback. It was required. Mandatory. The rules were the rules.

BUT — and this is the glow-up ✨ — those functions now start a new transaction automatically all on their own. No assist needed. Independent queens 💅 So SPI_start_transaction just chills there, keeping old code from breaking, no cap.

and that's the whole page, fr fr 🌈 this was PostgreSQL 18.6 documentation, dated 2026 🎀 mwah, bye bestie, go write some slay code 💖🦋✨