Re: Documenting when to retry on serialization failure
Simon Riggs <simon.riggs@enterprisedb.com>
From: Simon Riggs <simon.riggs@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Thomas Munro <thomas.munro@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2022-03-24T10:43:54Z
Lists: 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/
Commits
-
Doc: add some documentation about serialization failure handling.
- 0adb3dc68bfb 15.0 landed
-
Detect SSI conflicts before reporting constraint violations
- fcff8a575198 9.6.0 cited