| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Haumacher, Bernhard" <haui(at)haumacher(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Error on failed COMMIT |
| Date: | 2020-02-17 23:30:04 |
| Message-ID: | 20200217233004.GA18544@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Feb-14, Dave Cramer wrote:
> On Fri, 14 Feb 2020 at 15:19, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
> wrote:
>
> > Do you mean "if con.commit() results in a rollback, then an exception is
> > thrown, unless the parameter XYZ is set to PQR"?
>
> No. JDBC has a number of connection parameters which change internal
> semantics of various things.
>
> I was proposing to have a connection parameter which would be
> throwExceptionOnFailedCommit (or something) which would do what it says.
>
> None of this would touch the server. It would just change the driver
> semantics.
That's exactly what I was saying.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-02-17 23:42:20 | Re: pgindent && weirdness |
| Previous Message | Jesse Zhang | 2020-02-17 22:57:59 | Re: Resolving the python 2 -> python 3 mess |