| From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Documenting when to retry on serialization failure |
| Date: | 2021-12-29 12:39:39 |
| Message-ID: | CANbhV-EQhSdfD+GGjyZfvMqtvOiXi1ovwvPCXayMu1G_Hmb6aQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 29 Dec 2021 at 03:30, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
>
> On Fri, Dec 10, 2021 at 1:43 AM Simon Riggs
> <simon(dot)riggs(at)enterprisedb(dot)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 | Content-Type | Size |
|---|---|---|
| retryable_error_docs.v1.patch | application/octet-stream | 2.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2021-12-29 13:46:40 | Re: Throttling WAL inserts when the standby falls behind more than the configured replica_lag_in_bytes |
| Previous Message | Amul Sul | 2021-12-29 12:07:48 | Re: generalized conveyor belt storage |