SPI_ROLLBACK(3)

πŸ“¦ version 14.24, in opensuse-leap 16.0

🌸 NAME 🌸

SPI_rollback, SPI_rollback_and_chain β€” abort the current transaction. This is the SPI_ROLLBACK(3) page from the PostgreSQL 14.24 docs, and yes bestie, we’re getting into rollback lore πŸ’…βœ¨

πŸŽ€ SYNOPSIS πŸŽ€

void SPI_rollback(void)

void SPI_rollback_and_chain(void)

πŸ’– DESCRIPTION πŸ’–

Okay so 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 β€” the caller isn’t left stranded 🫢

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. Same energy, but the new transaction keeps the vibe of the old one ✨

These functions can only be executed if the SPI connection has been set as nonatomic in the call to SPI_connect_ext. That part is not optional, bestie β€” no nonatomic setup, no execution 😭


That’s the whole page, babe: SPI_ROLLBACK(3) from the PostgreSQL 14.24 documentation, dated 2026. Mwah πŸ’‹πŸŽ€

πŸ“¦ where this page comes from