pg_trigger stores triggers on tables
See CREATE TRIGGER
for more information.
|Row identifier (hidden attribute; must be explicitly selected)|
|The table this trigger is on|
|Trigger name (must be unique among triggers of same table)|
|The function to be called|
|Bit mask identifying trigger firing conditions|
Controls in which session_replication_role modes
the trigger fires.
|True if trigger is internally generated (usually, to enforce
the constraint identified by |
|The table referenced by a referential integrity constraint|
|The index supporting a unique, primary key, referential integrity, or exclusion constraint|
|True if constraint trigger is deferrable|
|True if constraint trigger is initially deferred|
|Number of argument strings passed to trigger function|
|Column numbers, if trigger is column-specific; otherwise an empty array|
|Argument strings to pass to trigger, each NULL-terminated|
|Expression tree (in |
Currently, column-specific triggering is supported only for
UPDATE events, and so
tgattr is relevant
only for that event type.
contain bits for other event types as well, but those are presumed
to be table-wide regardless of what is in
tgconstraint is nonzero,
largely redundant with the referenced
However, it is possible for a non-deferrable trigger to be associated
with a deferrable constraint: foreign key constraints can have some
deferrable and some non-deferrable triggers.
must be true if a relation has any triggers in this catalog.