Re: WIP: Detecting SSI conflicts before reporting constraint violations - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: WIP: Detecting SSI conflicts before reporting constraint violations
Date
Msg-id CACjxUsP-NV=55otAetdKRAMJge9SVDoXG9Nxepqy7_RDSrh4NQ@mail.gmail.com
Whole thread Raw
In response to Re: WIP: Detecting SSI conflicts before reporting constraint violations  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: WIP: Detecting SSI conflicts before reporting constraint violations
List pgsql-hackers
On Thu, Apr 7, 2016 at 3:26 AM, Simon Riggs <simon@2ndquadrant.com> wrote:

> We agree its a bug, so the deadline doesn't need to constrain us.

I'm not sure there is consensus across the community on that.

> I suggest we should apply what we have then fix the rest later
> when we work out how.

On that, I agree.  I will push what we have before the deadline
today, since it would cover about 90% of the SSI complaints I've
seen.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pgbench randomness initialization
Next
From: Fabien COELHO
Date:
Subject: Re: pgbench randomness initialization