| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Jeremy Schneider <schnjere(at)amazon(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: survey: psql syntax errors abort my transactions |
| Date: | 2020-07-03 06:46:34 |
| Message-ID: | 0f707f39184a972e8404061fac6bbce1635e7f93.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2020-07-02 at 09:31 -0700, Adrian Klaver wrote:
> I would say just add a message to the ERROR that points out
> ON_ERROR_ROLLBACK = 'on' is available. For instance:
>
> test(5432)=# begin ;
> BEGIN
> test(5432)=# select 1/0;
> ERROR: division by zero
> test(5432)=# select 1;
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
>
> New part of message
> HINT: \set ON_ERROR_ROLLBACK on to rollback on error.
-1
That would increase the already annoying spam of "current transaction is aborted"
messages when your transaction fails.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2020-07-03 06:54:22 | Re: survey: psql syntax errors abort my transactions |
| Previous Message | Adam Brusselback | 2020-07-03 00:02:31 | Re: Does TOAST really compress the complete row? |