public inbox for [email protected]  

help / color / mirror / Atom feed

From: Nathan Long <[email protected]>
To: Laurenz Albe <[email protected]>
Cc: [email protected]
Subject: Re: Clarify how triggers relate to transactions
Date: Wed, 28 Apr 2021 13:18:40 -0400
Message-ID: <CAOyE-6ZsrpJT2HRBRzGoixZDvRUYZnrvgRXFfZYs1WRW+rpZKQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

Gotcha. Where would I go to make the PR?

On Wed, Apr 28, 2021, 7:24 AM Laurenz Albe <[email protected]> wrote:

> On Tue, 2021-04-27 at 14:26 +0000, PG Doc comments form wrote:
> > 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."
>
> Good idea in principle, but I'd put that information on
> https://www.postgresql.org/docs/current/trigger-definition.html
>
> Yours,
> Laurenz Albe
>
>

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Clarify how triggers relate to transactions
  In-Reply-To: <CAOyE-6ZsrpJT2HRBRzGoixZDvRUYZnrvgRXFfZYs1WRW+rpZKQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox