DEALLOCATE(7)

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

πŸ’… DEALLOCATE(7) πŸ’…

okay bestie, welcome to the DEALLOCATE(7) page from the PostgreSQL 16.15 Documentation ✨ this one is short, sweet, and here to help you clean up your prepared statements πŸŽ€


πŸŽ€ NAME πŸŽ€

DEALLOCATE β€” deallocate a prepared statement 🫢

✨ SYNOPSIS ✨

DEALLOCATE [ PREPARE ] { name | ALL }

🌸 DESCRIPTION 🌸

DEALLOCATE is literally the command you use to deallocate a previously prepared SQL statement πŸ’– it's giving cleanup era, no cap.

If you do not explicitly deallocate a prepared statement, it gets deallocated when the session ends πŸ‘‘ so like, it won't just vibe forever.

For more info on prepared statements, go peek at PREPARE(7) πŸ¦‹

πŸ’œ PARAMETERS πŸ’œ

  • PREPARE β€” this key word is ignored πŸ™ˆ yes, bestie, it's just there and PostgreSQL is unbothered.
  • name β€” the name of the prepared statement you want to deallocate πŸŽ€
  • ALL β€” deallocate all prepared statements πŸ”₯ all of them, periodt.

🌈 COMPATIBILITY 🌈

The SQL standard includes a DEALLOCATE statement, but it is only for use in embedded SQL πŸ’… so that's the compatibility tea.

⭐ SEE ALSO ⭐

EXECUTE(7), PREPARE(7) 🧚 go check those out too, iykyk.


mwah πŸ’‹ signed, sealed, and slayed: PostgreSQL 16.15, dated 2026, page DEALLOCATE(7) πŸ’–βœ¨

πŸ“¦ where this page comes from