DROP_VIEW(7pg17)

🎀 NAME 🎀

omg bestie, this one is DROP_VIEW — aka DROP VIEW(7) — and it removes a view. Slay, but also be careful, because dropping things is very main-character energy. 💅

---

✨ SYNOPSIS ✨

DROP VIEW [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]

---

💖 DESCRIPTION 💖

DROP VIEW drops an existing view. That’s the whole vibe. But no cap: to run this command you must be the owner of the view. 👑

---

🦋 PARAMETERS 🦋

• IF EXISTS — do not throw an error if the view does not exist. In that case, a notice is issued. So it’s like “bestie, if it’s not there, don’t scream, just let it go.” 🫶
• name — the name of the view to remove. It can optionally be schema-qualified. Literally the target of the drop. 🎯
• CASCADE — automatically drop objects that depend on the view, such as other views, and in turn all objects that depend on those objects. See Section 5.15. It’s giving “consequences? yes, automatically.” 😭🔥
• RESTRICT — refuse to drop the view if any objects depend on it. This is the default. So by default it’s like “nope, something still needs you, we’re not doing this.” 💀

---

🌸 EXAMPLES 🌸

This command will remove the view called kinds:

DROP VIEW kinds;

iconic. short. effective. periodt. ✨

---

🌈 COMPATIBILITY 🌈

This command conforms to the SQL standard, except that the standard only allows one view to be dropped per command, and apart from the IF EXISTS option, which is a PostgreSQL extension. So yes, mostly standard, with a lil PostgreSQL flair. 💜

---

🔥 SEE ALSO 🔥

• ALTER VIEW (ALTER_VIEW(7))
• CREATE VIEW (CREATE_VIEW(7))

go read those too, bestie, iykyk 🧚💖

---

cute lil sign-off: this page is from the PostgreSQL 17.11 Documentation, dated 2026. mwah 💋🎀