Re: Documenting when to retry on serialization failure - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Documenting when to retry on serialization failure
Date
Msg-id CANbhV-EQhSdfD+GGjyZfvMqtvOiXi1ovwvPCXayMu1G_Hmb6aQ@mail.gmail.com
Whole thread Raw
In response to Re: Documenting when to retry on serialization failure  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Documenting when to retry on serialization failure  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, 29 Dec 2021 at 03:30, Thomas Munro <thomas.munro@gmail.com> wrote:
>
> On Fri, Dec 10, 2021 at 1:43 AM Simon Riggs
> <simon.riggs@enterprisedb.com> wrote:
> > "Applications using this level must be prepared to retry transactions
> > due to serialization failures."
> > ...
> > "When an application receives this error message, it should abort the
> > current transaction and retry the whole transaction from the
> > beginning."
> >
> > I note that the specific error codes this applies to are not
> > documented, so lets discuss what the docs for that would look like.
>
> +1 for naming the error.

I've tried to sum up the various points from everybody into this doc
patch. Thanks all for replies.

-- 
Simon Riggs                http://www.EnterpriseDB.com/

Attachment

pgsql-hackers by date:

Previous
From: Amul Sul
Date:
Subject: Re: generalized conveyor belt storage
Next
From: Stephen Frost
Date:
Subject: Re: Throttling WAL inserts when the standby falls behind more than the configured replica_lag_in_bytes