Re: Serializable Isolation without blocking

From: Greg Stark <stark(at)enterprisedb(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Michael Cahill <mjc(at)it(dot)usyd(dot)edu(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Serializable Isolation without blocking
Date: 2009-05-11 13:59:48
Message-ID: 4136ffa0905110659q5823f78m7ae6338b291e87b1@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 11, 2009 at 2:49 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> wrote:
>
>> All the authors show with regard to predicate handling is
>> handwaving,
>
> That is because predicate locking is a mature technology with many
> known implementations.  The best technique for any database product
> will depend on that product, and their technique doesn't depend on
> which implementation is used.  Assuming some form of predicate
> locking, do you have any other qualms about the the algorithm
> presented in the paper?

I thought the big problem with providing true serializability was the
predicate locking. If it doesn't address that need then does this get
us any closer?

Is this like saying walls are a well understood technology so these
antilock brakes work great for stopping your car as long as you
combine them with a wall? :)

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Albe Laurenz 2009-05-11 14:07:47 Re: Serializable Isolation without blocking
Previous Message Kevin Grittner 2009-05-11 13:49:52 Re: Serializable Isolation without blocking