Re: Documenting when to retry on serialization failure

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Documenting when to retry on serialization failure
Date: 2022-03-24 11:01:01
Message-ID: CA+hUKGLUioK+vepw7koWWQwSoumwf7Q-0Y6qKjvq6FthshYQCA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 24, 2022 at 11:44 PM Simon Riggs
<simon(dot)riggs(at)enterprisedb(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-03-24 11:01:47 Re: [PATCH] add relation and block-level filtering to pg_waldump
Previous Message Simon Riggs 2022-03-24 10:58:57 Re: Reducing power consumption on idle servers