CLOSE(7)

💖 CLOSE(7) 💖

okay so bestie, welcome to the PostgreSQL 14.24 Documentation page for CLOSE(7) — yes, we're doing cursors today and it's lowkey iconic. ✨

---

🌸 NAME 🌸

CLOSE — close a cursor. That's the whole vibe. 💅

🦋 SYNOPSIS 🦋

CLOSE { name | ALL }

🔥 DESCRIPTION 🔥

CLOSE frees the resources associated with an open cursor. After the cursor is closed, no subsequent operations are allowed on it. A cursor should be closed when it is no longer needed. Slay, cleanup era. 🧹💖

Every non-holdable open cursor is implicitly closed when a transaction is terminated by COMMIT or ROLLBACK. A holdable cursor is implicitly closed if the transaction that created it aborts via ROLLBACK. If the creating transaction successfully commits, the holdable cursor remains open until an explicit CLOSE is executed, or the client disconnects. That's the tea, fr fr. ☕

🎀 PARAMETERS 🎀

• name — the name of an open cursor to close. Bye bestie, you're done. 👋
• ALL — close all open cursors. Every single one. all of them. group logout energy. 💀✨

💜 NOTES 💜

PostgreSQL does not have an explicit OPEN cursor statement; a cursor is considered open when it is declared. Use the DECLARE statement to declare a cursor. no cap. 🫶

You can see all available cursors by querying the pg_cursors system view. little guest list, iykyk. 👑

If a cursor is closed after a savepoint which is later rolled back, the CLOSE is not rolled back; that is, the cursor remains closed. important caveat bestie, don't forget it. ⚠️

🌈 EXAMPLES 🌈

Close the cursor liahona:

CLOSE liahona;

👑 COMPATIBILITY 👑

CLOSE is fully conforming with the SQL standard. CLOSE ALL is a PostgreSQL extension. periodt. 💅

🦋 SEE ALSO 🦋

DECLARE(7), FETCH(7), MOVE(7)

---

that's the whole page, bestie. brought to you by PostgreSQL 14.24 Documentation, 2026 — mwah 💋✨