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-FP2te5L9JitWjswEpYDLd80WvRo4TUqzihfNh122dT_Q@mail.gmail.com
Whole thread Raw
In response to Re: Documenting when to retry on serialization failure  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Documenting when to retry on serialization failure
List pgsql-hackers
On Wed, 23 Mar 2022 at 19:50, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Simon Riggs <simon.riggs@enterprisedb.com> writes:
> > I've tried to sum up the various points from everybody into this doc
> > patch. Thanks all for replies.
>
> This seemed rather badly in need of copy-editing.  How do you
> like the attached text?

Seems clear and does the job.

The unique violation thing is worryingly general. Do we know enough to
say that this is thought to occur only with a) multiple unique
constraints, b) exclusion constraints?

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



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Logical replication timeout problem
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] add relation and block-level filtering to pg_waldump