Re: Clarify how triggers relate to transactions
Laurenz Albe <laurenz.albe@cybertec.at>
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: him@nathanmlong.com, pgsql-hackers@lists.postgresql.org
Date: 2021-05-20T15:53:40Z
Lists: pgsql-hackers, pgsql-docs
On Wed, 2021-05-05 at 11:55 +0200, Laurenz Albe wrote: > On Wed, 2021-04-28 at 13:24 +0200, Laurenz Albe wrote: > > On Tue, 2021-04-27 at 14:26 +0000, PG Doc comments form wrote: > > > 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." > > > > Good idea in principle, but I'd put that information on > > https://www.postgresql.org/docs/current/trigger-definition.html > > Here is a proposed patch for this. Replying to -hackers for the commitfest app. Yours, Laurenz Albe
Commits
-
Doc: clarify how triggers relate to transactions.
- 95bc40f880a6 14.0 landed
- 469150a240dd 15.0 landed