COMMIT_PREPARED(7pg18)

💖 COMMIT PREPARED(7) 💖

okay bestie, welcome to the PostgreSQL 18.6 Documentation for COMMIT PREPARED — it's the manual page, she's a whole queen, and she's about to explain how to actually finish a two-phase commit situation. no cap. let's go 🫶

---

✨ NAME ✨

COMMIT_PREPARED — commit a transaction that was earlier prepared for two-phase commit

---

🎀 SYNOPSIS 🎀

COMMIT PREPARED transaction_id

---

🌸 DESCRIPTION 🌸

so like, COMMIT PREPARED commits a transaction that is in prepared state. that's it. that's the whole vibe. you prepared it earlier, and now you're saying "okay bestie, we're actually doing this" 💅

---

🦋 PARAMETERS 🦋

• transaction_id — the transaction identifier of the transaction that is to be committed. that's the little name-tag your transaction is wearing. you need it. you can't just be like "commit the thing" and hope for the best 🙈

---

💜 NOTES 💜

listen up, because this part matters fr fr:

• To commit a prepared transaction, you must be either the same user that executed the transaction originally, or a superuser. but — plot twist — you do not have to be in the same session that executed the transaction. so you can slide in from a whole different session and still handle it. main character energy ✨
• This command cannot be executed inside a transaction block. nope. not allowed. the prepared transaction is committed immediately — no waiting, no queueing, it just happens ⚡
• All currently available prepared transactions are listed in the pg_prepared_xacts system view. that's your guest list, bestie — go check who's still waiting to be committed 👑

---

🌈 EXAMPLES 🌈

Commit the transaction identified by the transaction identifier foobar:

COMMIT PREPARED 'foobar';

look at her go. iconic. 🎀

---

⭐ COMPATIBILITY ⭐

COMMIT PREPARED is a PostgreSQL extension. it's 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 like… don't go expecting other databases to understand this. she's built different and she's proud of it 💅

---

👑 SEE ALSO 👑

• PREPARE TRANSACTION (PREPARE_TRANSACTION(7))
• ROLLBACK PREPARED (ROLLBACK_PREPARED(7))

---

💀 quick reminder bestie: the "must be the same user or a superuser" rule is not a suggestion. it's the law. respect it.

---

and that's the page!! this whole thing came from PostgreSQL 18.6, dated 2026 — thanks for reading, ily, go commit responsibly 🫶✨