Update on true serializable techniques in MVCC

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Update on true serializable techniques in MVCC
Date: 2009-12-15 19:02:34
Message-ID: 4B2788EA020000250002D51C@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Just to make those who care aware of it, here is Michael Cahill's
Doctoral Thesis based on implementing Serializable Snapshot
Isolation in InnoDB using a refined version of the techniques
previously used in the Berkley DB (and previously discussed on this
list):

http://hdl.handle.net/2123/5353

For those who missed the previous discussion, or don't remember it
well, this technique uses non-blocking SIREAD locks, which allow
true serializable behavior without increasing blocking beyond what
is present in normal MVCC snapshot isolation (readers do not block
writers, and vice versa), but generates some false positive
serialization errors. Apparently the number of false positives in
InnoDB is less than Berkeley DB because of the more fine-grained
locking in InnoDB.

Seriously, this post is just for the benefit of those who may be
interested in following these developments -- I don't have the
inclination or energy for another round of debate on the topic just
now. :-/

-Kevin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Scott Bailey 2009-12-15 19:31:05 Re: Range types
Previous Message Simon Riggs 2009-12-15 18:49:10 Hot Standby and prepared transactions