mvcc and lock - Mailing list pgsql-hackers

From postgresql
Subject mvcc and lock
Date
Msg-id 200303190807.AA51970282@rdb01.pku.edu.cn
Whole thread Raw
List pgsql-hackers
Hi all
I have read some code on transaction part.
When the new transaction starts, it record the snapshot of database containing the current transaction id,etc. So
dependingon the snapshot
 
, the transaction decide which tuple is visible.
But transaction could also be implemented by lock. so I am not sure how 
the transaction is implemented, by MVCC or Lock, or by both?
In my option, when tuple is processed in readonly mode(select), MVCC is enough. but when tuple is changed, lock is
used.I am not sure
 
whether the explanation is correct.
Thanks for any comments.
Best regards.
josh 




pgsql-hackers by date:

Previous
From: Dave Cramer
Date:
Subject: Re: cursors outside transactions
Next
From: Mike Meyer
Date:
Subject: Threaded Python vs. PostGreSQL plpython