Message-ID: <4ca26d9c2e7ce620236dd69f3eb746fc2dbcafb4.camel@cybertec.at>
Subject: Re: Clarify how triggers relate to transactions
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: him@nathanmlong.com, pgsql-hackers@lists.postgresql.org
Date: Thu, 20 May 2021 17:53:40 +0200
In-Reply-To: <62219f2ce78faf09687d998f347c518b3c08d067.camel@cybertec.at>
References: <161953360822.695.15805897835151971142@wrigleys.postgresql.org>
	 <1a565681fe54535d69e6418ef5ab55405b92beac.camel@cybertec.at>
	 <62219f2ce78faf09687d998f347c518b3c08d067.camel@cybertec.at>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/4ca26d9c2e7ce620236dd69f3eb746fc2dbcafb4.camel%40cybertec.at>
Precedence: bulk

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