> 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
On Tuesday, July 19, 2022, Håvar Nøvik 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 app
On Monday, July 18, 2022, Håvar Nøvik 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.
I've been wondering what the behavior of postgres is when the server process
stops, for whatever reason, at certain critical points in the execution flow.
In the following example the client will only regard the data as stored until
the COMMIT command is successfully executed. But the the server
