Re: WIP: Detecting SSI conflicts before reporting constraint violations

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(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 16:20:24
Message-ID: CACjxUsMHZYUc5o-dommjgMs7i7RznBRFD287ULjMf6veh1DrOw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 7, 2016 at 8:49 AM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:

> Here is a version that includes an attempt to describe the
> situation in the documentation.

Pushed with minor adjustments to the docs. Mostly I thought your
new text was more appropriate as just another paragraph than as a
"note". The previous paragraph was a little imprecise and was in
some conflict with the new one, so I adjusted that a little, too.

Nice work! I sure wish we had spotted that a one-line check there
would have covered so much when the feature was first added.

I understand there is considerable feeling that this should be
back-patched, but I have not done that pending a clear consensus on
the point, since it is a user-visible behavioral change.

--
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 Peter Eisentraut 2016-04-07 16:37:39 Re: pg_ctl promote wait
Previous Message Anastasia Lubennikova 2016-04-07 16:01:42 Re: WIP: Covering + unique indexes.