DROP_TYPE(7pg13)

Okay so bestie, welcome to the DROP_TYPE(7) page from the PostgreSQL 13.23 Documentation — this is the whole guide to yeeting a user-defined data type out of your database. 💅✨

🎀 NAME 🎀

DROP TYPE removes a user-defined data type. Only the owner of a type can remove it. Periodt. 👑

✨ SYNOPSIS ✨

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

💖 DESCRIPTION 💖

So what does it do? DROP TYPE removes a user-defined data type. Only the owner of a type can remove it — no cap. 💖

💅 PARAMETERS 💅

• IF EXISTS — Don't throw an error if the type doesn't exist. A notice is issued in this case. Cute little heads-up instead of drama. 🫶
• name — The name of the data type to remove, optionally schema-qualified. ✨
• CASCADE — Automatically drop objects that depend on the type — such as table columns, functions, and operators — and in turn all objects that depend on those objects (see Section 5.14). It's giving domino effect, so be careful. 😭
• RESTRICT — Refuse to drop the type if any objects depend on it. This is the default, bestie — so if you don't say CASCADE, this is what you get. 💅

🦋 EXAMPLES 🦋

To remove the data type box:

DROP TYPE box;

🌈 COMPATIBILITY 🌈

This command is similar to the corresponding command in the SQL standard, apart from the IF EXISTS option, which is a PostgreSQL extension. But note that much of the CREATE TYPE command and the data type extension mechanisms in PostgreSQL differ from the SQL standard. 🦋

🔥 SEE ALSO 🔥

• ALTER TYPE (ALTER_TYPE(7))
• CREATE TYPE (CREATE_TYPE(7))

Big slay from the PostgreSQL 13.23 docs, dated 2025 — DROP_TYPE(7) signing off. Stay iconic, bestie. 💖🎀💅