DROP_EVENT_TRIGGER(7pg15)

✨ NAME ✨

Okay so this is the PostgreSQL 15.19 docs page for DROP EVENT TRIGGER(7), and the main-character command here is DROP_EVENT_TRIGGER — it removes an event trigger. Periodt. 💅

🌸 SYNOPSIS 🌸

DROP EVENT TRIGGER [ IF EXISTS ] name [ CASCADE | RESTRICT ]

💖 DESCRIPTION 💖

DROP EVENT TRIGGER removes an existing event trigger. To execute this command, the current user must be the owner of the event trigger. No cap — owner vibes only. 👑

🎀 PARAMETERS 🎀

• IF EXISTS — do not throw an error if the event trigger does not exist. A notice is issued in this case. So it’s like, “bestie, it wasn’t there, but we’re not crashing over it.” 🫶
• name — the name of the event trigger to remove. Simple. Iconic. ✨
• CASCADE — automatically drop objects that depend on the trigger, and in turn all objects that depend on those objects (see Section 5.14). This one goes all the way down the dependency chain, so yeah, highkey powerful. 🔥
• RESTRICT — refuse to drop the trigger if any objects depend on it. This is the default. Safe and sound, lowkey the responsible queen. 🛡️

🦋 EXAMPLES 🦋

Destroy the trigger snitch:

DROP EVENT TRIGGER snitch;

Not the snitch getting dropped 😭💀 — but yes, that’s literally the example.

🌈 COMPATIBILITY 🌈

There is no DROP EVENT TRIGGER statement in the SQL standard. So this is very much a PostgreSQL-specific slay. 💫

💜 SEE ALSO 💜

• CREATE EVENT TRIGGER (CREATE_EVENT_TRIGGER(7))
• ALTER EVENT TRIGGER (ALTER_EVENT_TRIGGER(7))

💖 That’s the whole page, bestie — brought to you by PostgreSQL 15.19, dated 2026, and filed under DROP EVENT TRIGGER(7). Mwah! 💖