| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Florian Weimer" <fweimer(at)bfk(dot)de>, "Florian Pflug" <fgp(dot)phlo(dot)org(at)gmail(dot)com> |
| Cc: | "Nicolas Barbier" <nicolas(dot)barbier(at)gmail(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>, "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Subject: | Re: Update on true serializable techniques in MVCC |
| Date: | 2009-12-18 17:49:15 |
| Message-ID: | 4B2B6C3C020000250002D770@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Florian Weimer <fweimer(at)bfk(dot)de> wrote:
> * Florian Pflug:
>> On 16.12.09 16:40 , Kevin Grittner wrote:
>>> Nicolas Barbier<nicolas(dot)barbier(at)gmail(dot)com> wrote:
>>>
>>>> I am not sure whether the serialization failures that it may
>>>> cause are dependent on the plan used.
>>>
>>> They are.
>>
>> But so are failures due to deadlocks even today, no?
>
> They are detected. In this context, "serialization failure" means
> that PostgreSQL generates a history which lacks one-copy
> serializability, without reporting any errors. (In the general
> case, the unique constraint violation which bugs me personally is
> a different beast and does result in an error.)
I don't understand what you're saying here. Could you rephrase or
expand on this?
Thanks,
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-12-18 17:52:50 | Re: Time to run initdb is mostly figure-out-the-timezone work |
| Previous Message | Alvaro Herrera | 2009-12-18 17:49:04 | Re: Time to run initdb is mostly figure-out-the-timezone work |