SPI_ROLLBACK(3)

okay bestie, this is the SPI_ROLLBACK(3) page — manual name folded in near the top like a cute little bow 🎀. We’re talking about aborting the current transaction, and these two functions are lowkey carrying the whole rollback vibe. 💅

🌸 NAME 🌸

SPI_rollback, SPI_rollback_and_chain — abort the current transaction. periodt.

✨ SYNOPSIS ✨

void SPI_rollback(void)

void SPI_rollback_and_chain(void)

💖 DESCRIPTION 💖

SPI_rollback rolls back the current transaction. It is approximately equivalent to running the SQL command ROLLBACK. 🫶 After the transaction is rolled back, a new transaction is automatically started using default transaction characteristics, so that the caller can continue using SPI facilities. slay, continuity.

SPI_rollback_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 ROLLBACK AND CHAIN. it’s giving chain reaction, but make it transaction-safe 🔥.

⚠️ 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. no nonatomic setting, no rollback party 💀.

PostgreSQL 15.19 · 2026 · that’s the source/version and date, bestie — stay slay and keep those transactions aborted correctly 💅✨