ALTER_EVENT_TRIGGER(7pg16)
π 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 alsosession_replication_role.
π COMPATIBILITY π
There is no ALTER EVENT TRIGGER statement in the SQL standard. Thatβs it, thatβs the tea β
π«Ά SEE ALSO π«Ά
CREATE EVENT TRIGGER(CREATE_EVENT_TRIGGER(7))DROP EVENT TRIGGER(DROP_EVENT_TRIGGER(7))
π 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
- opensuse-leap 16.0: postgresql16 16.15-160000.1.1 Β· PostgreSQL
- opensuse-leap 16.0: postgresql16 16.15-160000.1.1 Β· PostgreSQL
- opensuse-leap 16.0: postgresql16 16.15-160000.1.1 Β· PostgreSQL
- opensuse-leap 16.0: postgresql16 16.15-160000.1.1 Β· PostgreSQL
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms