Serializable use of Read Committed isolation level

Several DBMS engines use Read Committed (RC) as a default isolation level, risking the loss of data integrity but allowing more concurrency. We propose ways to preanalyse (and then modify) the code of a set of applications, that will allow us to run at RC isolation and still guarantee that all executions are serializable. Our experiments show performance that is significantly higher than from traditional ways that ensure correctness by directly using stronger isolation mechanisms (two-phase locking or snapshot isolation) that might be available in the engine. The overhead of our approach compared to RC on unmodified application programs is typically only about 5-10%.