Re: Review: pre-commit triggers - Mailing list pgsql-hackers

From Ian Lawrence Barwick
Subject Re: Review: pre-commit triggers
Date
Msg-id CAB8KJ=j3s98YrGqEFx+9KhPPSmzwCp4zs-X4vXBc6XtMp5Wraw@mail.gmail.com
Whole thread Raw
In response to Re: Review: pre-commit triggers  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2013/11/20 Tom Lane <tgl@sss.pgh.pa.us>:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Mon, Nov 18, 2013 at 9:39 AM, Ian Lawrence Barwick <barwick@gmail.com> wrote:
>>> I'd expect this to lead to a failed transaction block,
>>> or at least some sort of notice that the transaction itself
>>> has been rolled back.
>
>> Ending up in a failed transaction block would be wrong.  If the user
>> does a BEGIN, a bunch of stuff, and a COMMIT, they're entitled to
>> assume without checking that they are no longer in a transaction
>> block.
>
> Absolutely.  There are plenty of ways to fail at COMMIT already,
> eg deferred foreign key constraints.  This shouldn't act any
> different.

Ah OK, I see how that works. Thanks for the explanation.

Ian Barwick



pgsql-hackers by date:

Previous
From: Haribabu kommi
Date:
Subject: Re: New option for pg_basebackup, to specify a different directory for pg_xlog
Next
From: "Etsuro Fujita"
Date:
Subject: Re: Get more from indices.