| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Dave Cramer <davecramer(at)postgres(dot)rocks>, Robert Haas <robertmhaas(at)gmail(dot)com>, Shay Rojansky <roji(at)roji(dot)org>, "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-25 05:58:43 |
| Message-ID: | CAB=Je-FOmN5hq3gwDQm=gCzg=CzDhTxE0yxXdR1ThYmHayTxBw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>do you think most common connection poolers would continue to
>work after making this change?
Of course, they should.
There are existing cases when commit responds with an error: deferrable
constraints.
There's nothing new except it is suggested to make the behavior of
commit/prepare failure (e.g. "can't commit the transaction because...")
consistent with other commit failures (e.g. deferred violation).
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-02-25 06:45:39 | Re: Error on failed COMMIT |
| Previous Message | Aditya Toshniwal | 2020-02-25 05:23:35 | Re: PG v12.2 - Setting jit_above_cost is causing the server to crash |