Postgres Pro
Downloads
Home   >   mailing lists

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

From Thomas Munro
Subject Re: Documenting when to retry on serialization failure
Date
Msg-id CA+hUKGLUioK+vepw7koWWQwSoumwf7Q-0Y6qKjvq6FthshYQCA@mail.gmail.com
Whole thread Raw
In response to Re: Documenting when to retry on serialization failure  (Simon Riggs <simon.riggs@enterprisedb.com>)
Responses Re: Documenting when to retry on serialization failure  (Simon Riggs <simon.riggs@enterprisedb.com>)
Re: Documenting when to retry on serialization failure  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Thu, Mar 24, 2022 at 11:44 PM Simon Riggs
<simon.riggs@enterprisedb.com> wrote:
> 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?

I'm aware of 3 cases.  The two you mentioned, which I think we can fix
(as described in the threads I posted upthread), and then there is a
third case that I'm still confused about, in the last line of
read-write-unique-4.spec.

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Reducing power consumption on idle servers
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] add relation and block-level filtering to pg_waldump