Re: Update on true serializable techniques in MVCC - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Update on true serializable techniques in MVCC
Date
Msg-id 4B2B6C3C020000250002D770@gw.wicourts.gov
Whole thread Raw
In response to Re: Update on true serializable techniques in MVCC  (Florian Weimer <fweimer@bfk.de>)
List pgsql-hackers
Florian Weimer <fweimer@bfk.de> wrote:
> * Florian Pflug:
>> On 16.12.09 16:40 , Kevin Grittner wrote:
>>> Nicolas Barbier<nicolas.barbier@gmail.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


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Time to run initdb is mostly figure-out-the-timezone work
Next
From: Tom Lane
Date:
Subject: Re: Time to run initdb is mostly figure-out-the-timezone work