| From: | Håvar Nøvik <havar(at)novik(dot)email> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: How to handle failed COMMIT |
| Date: | 2022-07-19 14:52:13 |
| Message-ID: | 094c9333-d7f5-4294-961a-54a0cd90b612@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Correct, the client did not get confirmation of commit success so it must operate as if it failed.
I mean that’s the point, the client can’t operate as if it failed. It must operate as the state is unknown. But maybe that’s the correct application behaviour, just that I haven’t thought this through previously.
/Håvar Nøvik
On Tue, Jul 19, 2022, at 16:12, David G. Johnston wrote:
> On Monday, July 18, 2022, Håvar Nøvik <havar(at)novik(dot)email> wrote:
>>
>> try
>> execute transactional sql
>> catch (commit failed)
>> if (data is not stored)
>> // regard data as not stored
>
> Correct, the client did not get confirmation of commit success so it must operate as if it failed.
>
> David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-07-19 14:57:25 | Re: How to handle failed COMMIT |
| Previous Message | Tom Lane | 2022-07-19 14:23:34 | Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity |