SPI_START_TRANSACTION(3pg14)

💅 SPI_START_TRANSACTION 💅

okay so bestie, buckle up, because we're in the PostgreSQL 14 docs (yes, the 3pg14 girlies, iykyk) and today's main character is a function that literally does nothing. no cap. let's get into it 🎀

✨ NAME ✨

SPI_start_transaction — the obsolete function. she's retired, she's iconic, she's still on the invite list for compatibility reasons 🫶

🌸 SYNOPSIS 🌸

void SPI_start_transaction(void)

that's it. that's the whole vibe. no arguments, no return value, nothing to pass in. void in, void out, slay 💅

🦋 DESCRIPTION 🦋

so here's the tea: SPI_start_transaction does nothing. like, genuinely nothing. she exists purely for code compatibility with earlier PostgreSQL releases — a little nostalgia keepsake for your old codebases so they don't break when they see her name 🥺

fr fr, if you're expecting this to start a transaction, bestie, it does NOT. don't be out here relying on it 😭

back in the day, you had to call her after calling SPI_commit or SPI_rollback. it was required. mandatory. the whole thing. but now? SPI_commit and SPI_rollback start a new transaction automatically, all by themselves, no assistance needed 👑 so this function just hangs out, looking cute, keeping your old code compiling ✨

okay that's the whole page, it's short, it's sweet, it's giving "placeholder emoji in the group chat" energy 🧚

sign-off 💖: this little legend comes to you from the PostgreSQL 14.24 documentation, dated 2026, and yes, she's still here, still doing nothing, still iconic. periodt. 💜