| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: ON_ERROR_ROLLBACK |
| Date: | 2014-12-29 17:16:20 |
| Message-ID: | 54A18C64.9020406@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 12/29/2014 08:51 AM, Adrian Klaver wrote:
> While working on the thread 'Rollback on include error in psql' I ran across something I am not sure with regards to ON_ERROR_ROLLBACK:
>
>
> 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?
>
Should have mentioned Postgres version is 9.3.5
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | wetter wetterana | 2014-12-29 17:22:28 | "ERROR: could not read block 4459549 in file "base/16384/16956.34": Result too large" |
| Previous Message | Alvaro Herrera | 2014-12-29 17:09:25 | Re: pg_base_backup limit bandwidth possible? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-12-29 17:29:07 | Re: replicating DROP commands across servers |
| Previous Message | Kevin Grittner | 2014-12-29 16:53:24 | Re: BUG #12330: ACID is broken for unique constraints |