| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Håvar Nøvik <havar(at)novik(dot)email> |
| 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:57:25 |
| Message-ID: | CAKFQuwbBjVsEcedoPzLyb9WvAKgJBYwg6-8XQ218aJqExuNWfg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tuesday, July 19, 2022, Håvar Nøvik <havar(at)novik(dot)email> wrote:
> > 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.
>
Right, since you sent commit there is now a non-zero chance the data is
committed but the client is unaware of that fact.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2022-07-19 15:00:43 | Re: Out Of Memory |
| Previous Message | Håvar Nøvik | 2022-07-19 14:52:13 | Re: How to handle failed COMMIT |