From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | him(at)nathanmlong(dot)com |
Subject: | Clarify how triggers relate to transactions |
Date: | 2021-04-27 14:26:48 |
Message-ID: | 161953360822.695.15805897835151971142@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/sql-createtrigger.html
Description:
https://www.postgresql.org/docs/current/sql-createtrigger.html mentions the
word "transaction" only once, in reference specifically to constraint
triggers: "They can be fired either at the end of the statement causing the
triggering event, or at the end of the containing transaction; in the latter
case they are said to be deferred."
If I understand correctly, it would be helpful to add this sentence or a
corrected version of it: "Triggers always execute in the same transaction as
the triggering event, and if a trigger fails, the transaction is rolled
back."
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2021-04-28 11:24:53 | Re: Clarify how triggers relate to transactions |
Previous Message | Laurenz Albe | 2021-04-27 09:28:37 | Re: "68.4. Visibility Map" change suggestion. |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2021-04-27 14:29:07 | Re: Replication slot stats misgivings |
Previous Message | Bharath Rupireddy | 2021-04-27 14:07:27 | Should we document the behaviour of TRUNCATE skipping repeated relations? |