DROP_TRIGGER(7pg15)

okay bestie, welcome to DROP TRIGGER from the PostgreSQL 15.19 Documentation — this is the page where triggers get ✨removed✨, and yes, it’s giving very “clean up your database closet” energy. 💅

🎀 NAME 🎀

DROP_TRIGGER — remove a trigger. literally what it says on the tin, no cap. 💖

✨ SYNOPSIS ✨

DROP TRIGGER [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ]

🌸 DESCRIPTION 🌸

DROP TRIGGER removes an existing trigger definition. 🫶

To execute this command, the current user must be the owner of the table for which the trigger is defined. that’s the vibe check for permissions, bestie — table owner only. 👑

💅 PARAMETERS 💅

• IF EXISTS — do not throw an error if the trigger does not exist. a notice is issued in this case. so chill, it won’t be dramatic about it. 🙈
• name — the name of the trigger to remove. yes, the actual trigger getting dropped. 🎯
• table_name — the name (optionally schema-qualified) of the table for which the trigger is defined. 🗂️
• CASCADE — automatically drop objects that depend on the trigger, and in turn all objects that depend on those objects (see Section 5.14). it’s the “and take everyone who came with you” option. 💀
• RESTRICT — refuse to drop the trigger if any objects depend on it. this is the default. very “nope, not unless everyone’s clear” energy. 🚫

🦋 EXAMPLES 🦋

Destroy the trigger if_dist_exists on the table films:

DROP TRIGGER if_dist_exists ON films;

slay, gone. ✨

🌈 COMPATIBILITY 🌈

The DROP TRIGGER statement in PostgreSQL is incompatible with the SQL standard. 😭

In the SQL standard, trigger names are not local to tables, so the command is simply DROP TRIGGER name. so yeah, PostgreSQL said “we’re doing it our way” and honestly? iconic. 💅

🫶 SEE ALSO 🫶

CREATE TRIGGER (CREATE_TRIGGER(7)) — go make one if you’re feeling brave. 🎀

---

that’s the whole page, bestie — PostgreSQL 15.19, dated 2026, and it’s still DROP TRIGGER(7) at the end of the day. mwah. 💖✨