Re: ON_ERROR_ROLLBACK

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: ON_ERROR_ROLLBACK
Date: 2014-12-29 21:24:57
Message-ID: 54A1C6A9.6020705@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 12/29/2014 09:55 AM, Tom Lane wrote:
> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
>> So it seems you can turn ON_ERROR_ROLLBACK on with either 1 or 'on', but you can only turn it off with 'off'.
>> With ON_ERROR_STOP 1/on and 0/off both seem to work.
>
>> Is this expected?
>

>
> Given the lack of previous complaints, this probably isn't backpatching
> material, but it sure seems like a bit of attention to consistency
> would be warranted here.

I would appreciate it, thanks.

>
> regards, tom lane
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2014-12-29 22:07:54 Re: [GENERAL] Rollback on include error in psql
Previous Message Kevin Grittner 2014-12-29 19:31:49 Re: "ERROR: could not read block 4459549 in file "base/16384/16956.34": Result too large"

Browse pgsql-hackers by date

  From Date Subject
Next Message Adam Brightwell 2014-12-29 21:34:14 Re: Additional role attributes && superuser review
Previous Message Merlin Moncure 2014-12-29 20:07:44 Re: BUG #12330: ACID is broken for unique constraints