Re: WIP: Detecting SSI conflicts before reporting constraint violations

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, David Steele <david(at)pgmasters(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: Detecting SSI conflicts before reporting constraint violations
Date: 2016-04-07 10:42:32
Message-ID: CACjxUsP-NV=55otAetdKRAMJge9SVDoXG9Nxepqy7_RDSrh4NQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 7, 2016 at 3:26 AM, Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2016-04-07 11:01:44 Re: pgbench randomness initialization
Previous Message Andres Freund 2016-04-07 10:38:21 Re: pgbench randomness initialization