ROLLBACK_PREPARED(7pg17)

🦋 NAME 🦋

Okay bestie, welcome to ROLLBACK PREPARED(7) — aka the ROLLBACK_PREPARED(7pg17) page — the manual for ROLLBACK PREPARED. It cancels a transaction that was earlier prepared for two-phase commit. Periodt. 💅

---

✨ SYNOPSIS ✨

ROLLBACK PREPARED transaction_id

---

🌸 DESCRIPTION 🌸

ROLLBACK PREPARED rolls back a transaction that is in prepared state. That’s the tea, no cap. 🫶

---

🎀 PARAMETERS 🎀

• transaction_id — the transaction identifier of the transaction that is to be rolled back. Literally the name-tag for the prepared transaction you’re sending home. 🏠

---

🔥 NOTES 🔥

• To roll back a prepared transaction, you must be either the same user that executed the transaction originally, or a superuser. But you do not have to be in the same session that executed the transaction. Different session? Fine. Different user? Only if you’re a superuser. 👑
• This command cannot be executed inside a transaction block. Not me trying to nest this — it’s a no. 🙈 The prepared transaction is rolled back immediately.
• All currently available prepared transactions are listed in the pg_prepared_xacts system view. That’s your little guest list, iykyk. 📋

⚠️ Friendly lil warning: no transaction block for this one — it has main character energy and has to run on its own.

---

🍓 EXAMPLES 🍓

Roll back the transaction identified by the transaction identifier foobar:

ROLLBACK PREPARED 'foobar';

Slay. That’s the whole example. 💖

---

🌈 COMPATIBILITY 🌈

ROLLBACK PREPARED is a PostgreSQL extension. It is intended for use by external transaction management systems, some of which are covered by standards (such as X/Open XA), but the SQL side of those systems is not standardized. So it’s giving “very useful, but not standardized SQL-side,” fr fr. ✨

---

👀 SEE ALSO 👀

• PREPARE TRANSACTION (PREPARE_TRANSACTION(7))
• COMMIT PREPARED (COMMIT_PREPARED(7))

---

That’s the whole page, bestie — brought to you by PostgreSQL 17.11, dated 2026. Iconic source/version energy, mwah 💜🎀