| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)gmail(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 13:49:32 |
| Message-ID: | CAEepm=3ZkkeWQwrM+JUKMqH8ECJLZhguwb12U-eaAcx45nbAiQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 7, 2016 at 10:42 PM, Kevin Grittner <kgrittn(at)gmail(dot)com> wrote:
> 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.
Here is a version that includes an attempt to describe the situation
in the documentation. The first three sentences highlight the general
problem and apply to all versions since 9.1. Then the rest of the
paragraph beginning "This can be avoided ..." describes the improved
situation in 9.6 if this patch is committed.
--
Thomas Munro
http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| ssi-read-write-unique-v5.patch | application/octet-stream | 12.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2016-04-07 13:50:44 | Re: Move PinBuffer and UnpinBuffer to atomics |
| Previous Message | Merlin Moncure | 2016-04-07 13:48:28 | Re: Why the "UPDATE tab SET tab.col" is invalid? |