ALTER_EVENT_TRIGGER(7pg16)

πŸ“¦ version 16.15, in opensuse-leap 16.0

πŸ’… ALTER EVENT TRIGGER πŸ’…

okay so this is the ALTER_EVENT_TRIGGER(7pg16) page β€” aka ALTER EVENT TRIGGER(7) β€” from the PostgreSQL 16.15 Documentation, and it is literally giving β€œlet me tweak my event trigger’s whole deal” ✨ You’re in the right group chat, bestie 🫢


πŸŽ€ NAME πŸŽ€

ALTER_EVENT_TRIGGER β€” change the definition of an event trigger

🌈 SYNOPSIS 🌈

ALTER EVENT TRIGGER name DISABLE
ALTER EVENT TRIGGER name ENABLE [ REPLICA | ALWAYS ]
ALTER EVENT TRIGGER name OWNER TO { new_owner | CURRENT_ROLE | CURRENT_USER | SESSION_USER }
ALTER EVENT TRIGGER name RENAME TO new_name

✨ DESCRIPTION ✨

ALTER EVENT TRIGGER changes properties of an existing event trigger. periodt, that’s the whole point of this icon πŸ’…

You must be superuser to alter an event trigger. No cap: superuser privileges are required, bestie πŸ‘‘

πŸ¦‹ PARAMETERS πŸ¦‹

  • name β€” the name of an existing trigger to alter. iykyk, it’s the one you’re changing.
  • new_owner β€” the user name of the new owner of the event trigger.
  • new_name β€” the new name of the event trigger.
  • DISABLE/ENABLE [ REPLICA | ALWAYS ] β€” these forms configure the firing of event triggers. A disabled trigger is still known to the system, but is not executed when its triggering event occurs. See also session_replication_role.

πŸ’€ COMPATIBILITY πŸ’€

There is no ALTER EVENT TRIGGER statement in the SQL standard. That’s it, that’s the tea β˜•

🫢 SEE ALSO 🫢


πŸ’– source/version: PostgreSQL 16.15 Β· date: 2026 πŸ’– β€” footer facts, delivered cute. Now go alter those event triggers, bestie, and slay βœ¨πŸ‘‘

πŸ“¦ where this page comes from