Subject Re: "Write Committed" transaction mode
Author hvlad
> The algorithm is simple, though the details might not be. When a record
> is fetched "for update" in write committed mode:
>
> 1. Look at the head record version. If the transaction that created
> it is committed, do a dummy update and return.

Is this dummy update made when page is locked for fetch ?

I mean, what is exact order of events :

fetch page for read
extract record
release page lock
validate booleans
fetch page for write
create stub
release page lock
return record to caller

or

fetch page for write
create stub
extract record
release page lock
validate booleans
return record to caller

or may be something else ?

Thanks,
Vlad