Re: consistent reads and unique key updates
Date: Wed, 25 Apr 2012 23:20:06 +0100
> ok, just rerun the test but same output :-S
> end of the test and final query session statistics:
I don't think I've seen a reference to the version number - but I may have missed some posts; I don't think you've shown any execution plans for the query or update.
However, one possibility is this: the update may have used the "switch current to new buffer mechanism" to clone the current copy, switching the original copy to state CR. If the first session then accessed the original it would be in the correct state for it to read without applying any undo.
In earlier versions of Oracle I think the update would have to do a tablescan for the 'switch current' to occur, and the first session would have had to do a "set transaction read only".