"Serializable Snapshot Isolation in PostgreSQL" presentation at VLDB in Istanbul - Mailing list pgsql-advocacy

From the abstract that you can also find here:
 
http://sacan.biomed.drexel.edu/vldb2012/program.php#Industrial_Session_Abstracts
 
 
>> Serializable Snapshot Isolation in PostgreSQL
   Dan Ports (MIT CSAIL), Kevin Grittner (Wisconsin Supreme Court)

This paper describes our experience implementing PostgreSQL’s new
serializable isolation level. It is based on the recently-developed
Serializable Snapshot Isolation (SSI) technique. This is the first
implementation of SSI in a production database release as well as the
first in a database that did not previously have a lock-based
serializable isolation level. We reflect on our experience and
describe how we overcame some of the resulting challenges, including
the implementation of a new lock manager, a technique for ensuring
memory usage is bounded, and integration with other PostgreSQL
features. We also introduce an extension to SSI that improves
performance for read-only transactions. We evaluate PostgreSQL’s
serializable isolation level using several benchmarks and show that
it achieves performance only slightly below that of snapshot
isolation, and significantly outperforms the traditional two-phase
locking approach on read-intensive workloads.
 
 
I notice that many of the other papers and demonstrations involve
implementations of the ideas in PostgreSQL.  I'll try to attend those
sessions where possible, and see if any of these ideas seem "ripe"
for core enhancements and free of conflicting IP claims.
 
-Kevin