DROP_MATERIALIZED_VIEW(7pg16)

💖 NAME 💖

okay bestie, welcome to the DROP_MATERIALIZED_VIEW(7) page from the PostgreSQL 16.15 Documentation. This command is literally called DROP_MATERIALIZED_VIEW, and its whole vibe is: remove a materialized view. 💅

🌸 SYNOPSIS 🌸

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

✨ DESCRIPTION ✨

DROP MATERIALIZED VIEW drops an existing materialized view. To execute this command you must be the owner of the materialized view. no cap, that's the rule. 🫶

🎀 PARAMETERS 🎀

• IF EXISTS — do not throw an error if the materialized view does not exist. A notice is issued in this case. 🙈
• name — the name (optionally schema-qualified) of the materialized view to remove. ✨
• CASCADE — automatically drop objects that depend on the materialized view (such as other materialized views, or regular views), and in turn all objects that depend on those objects (see Section 5.14). 🔥
• RESTRICT — refuse to drop the materialized view if any objects depend on it. This is the default. 💀

💅 EXAMPLES 💅

This command will remove the materialized view called order_summary:

DROP MATERIALIZED VIEW order_summary;

🔥 COMPATIBILITY 🔥

DROP MATERIALIZED VIEW is a PostgreSQL extension. 🌈

🫶 SEE ALSO 🫶

• CREATE MATERIALIZED VIEW (CREATE_MATERIALIZED_VIEW(7))
• ALTER MATERIALIZED VIEW (ALTER_MATERIALIZED_VIEW(7))
• REFRESH MATERIALIZED VIEW (REFRESH_MATERIALIZED_VIEW(7))

that's the whole DROP_MATERIALIZED_VIEW(7) situation, bestie. This page is from PostgreSQL 16.15, dated 2026, footer energy: DROP MATE...IZED VIEW(7). go be the owner of your materialized views and slay 💖✨