SPI_COMMIT(3)

💅 NAME 💅

Okay bestie, welcome to SPI_COMMIT(3) — the page all about SPI_commit and SPI_commit_and_chain, aka the functions that commit the current transaction. Slay. ✨

🎀 SYNOPSIS 🎀

void SPI_commit(void)

void SPI_commit_and_chain(void)

🌸 DESCRIPTION 🌸

So SPI_commit commits the current transaction. It’s approximately equivalent to running the SQL command COMMIT. No cap. 💅

After the transaction is committed, a new transaction is automatically started using default transaction characteristics, so that the caller can keep using SPI facilities. Iconic, honestly. 🦋

But listen — if there is a failure during commit, the current transaction is instead rolled back and a new transaction is started, after which the error is thrown in the usual way. So it’s giving “commit, but make it resilient.” 😭✨

SPI_commit_and_chain is the same, but the new transaction is started with the same transaction characteristics as the just finished one, like with the SQL command COMMIT AND CHAIN. Periodt. 🔥

Heads up, bestie: these functions can only be executed if the SPI connection has been set as nonatomic in the call to SPI_connect_ext. That’s the vibe check you gotta pass first. 🫶

Written for PostgreSQL 13.23, dated 2025 — mwah, she’s iconic, she’s documented, she’s logging off. 💖🎀✨