For many applications, read committed is the most appropriate isolation level. Read
committed isolation can provide considerably more concurrency with a somewhat
increased risk of inconsistent results due to phantoms and non-repeatable reads for
Many high-performance environments with high transaction arrival rates require more
throughput and faster response times than can be achieved with serializable isolation.
Other environments that supports users with a very low transaction arrival rate also
face very low risk of incorrect results due to phantoms and nonrepeatable reads. Read
committed isolation is suitable for both of these environments.
Oracle read committed isolation provides transaction set consistency for every query.
That is, every query sees data in a consistent state. Therefore, read committed isolation
will suffice for many applications that might require a higher degree of isolation if run
on other database management systems that do not use multiversion concurrency
Read committed isolation mode does not require application logic to trap the Cannot
serialize access error and loop back to restart a transaction. In most applications,
few transactions have a functional need to issue the same query twice, so for many
applications protection against phantoms and non-repeatable reads is not important.
Therefore many developers choose read committed to avoid the need to write such
error checking and retry code in each transaction.
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/10599713/viewspace-989863/，如需转载，请注明出处，否则将追究法律责任。