mirror of
https://github.com/postgres/postgres.git
synced 2025-08-31 17:02:12 +03:00
Doc: clarify how triggers relate to transactions.
Laurenz Albe, per gripe from Nathan Long. Discussion: https://postgr.es/m/161953360822.695.15805897835151971142@wrigleys.postgresql.org
This commit is contained in:
@@ -122,6 +122,15 @@
|
||||
row in the view is identified as needing to be operated on.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The execution of an <literal>AFTER</literal> trigger can be deferred
|
||||
to the end of the transaction, rather than the end of the statement,
|
||||
if it was defined as a <firstterm>constraint trigger</firstterm>.
|
||||
In all cases, a trigger is executed as part of the same transaction as
|
||||
the statement that triggered it, so if either the statement or the
|
||||
trigger causes an error, the effects of both will be rolled back.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
A statement that targets a parent table in an inheritance or partitioning
|
||||
hierarchy does not cause the statement-level triggers of affected child
|
||||
|
Reference in New Issue
Block a user