According to this articale serializable isolation level performs read lock as well as range lock on rows. So, if in one transaction I perform SELECT statement on some rows(or row), another transactions that will try to query the same rows(or subset of that rows) will lock untill the first one makes a commit or rollback. Right? But in oracle I try to perform such scenario and second transaction have not been locked. Why it doesn’t lock until I perform commit in first transaction?
According to this articale serializable isolation level performs read lock as well as range
Share
Oracle employs multiversionning to guarantee read-consitency without blocking writes:
When you perform a SELECT in Read-Committed isolation, the database reconstructs the rows as they were at the beginning of the query so that you have a consistent view of the data (all blocks are retrieved at the same point-in-time). Oracle uses undo data to reverse the changes made to the blocks after the query began (also the changes from other uncommited transactions).
The principle is the same with the serializable transaction isolation except that Oracle reconstructs the rows as they were at the beginning of the transaction.
For further reading, I suggest you take a look at the “Multi-Versioning and Concurrency” chapter from one of Tom Kyte’s book.