SPI_COMMIT(3)

💖 SPI_COMMIT(3) 💖

okay so welcome to the SPI_COMMIT(3) page from the PostgreSQL 15.19 Documentation, bestie — this one is short, sweet, and all about committing the current transaction. no cap. 🫶

🌸 NAME 🌸

SPI_commit, SPI_commit_and_chain — commit the current transaction

✨ SYNOPSIS ✨

void SPI_commit(void)

void SPI_commit_and_chain(void)

🦋 DESCRIPTION 🦋

SPI_commit commits the current transaction. it's approximately equivalent to running the SQL command COMMIT. after the transaction is committed, a new transaction is automatically started using default transaction characteristics, so that the caller can continue using SPI facilities. 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. 😭

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. it's giving "commit, but keep the vibe going" energy. ✨

⚠️ important vibe check: these functions can only be executed if the SPI connection has been set as nonatomic in the call to SPI_connect_ext. don't skip that part, bestie. 💅

🫶 and that's the whole page, bestie — brought to you by PostgreSQL 15.19, dated 2026, and signed off with SPI_COMMIT(3) energy. periodt. 💖