Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> comp.databases.theory -> Re: Lock-free databases

Re: Lock-free databases

From: Christopher Browne <cbbrowne_at_acm.org>
Date: Sat, 05 Nov 2005 11:05:45 -0500
Message-ID: <m3d5lf84h2.fsf@mobile.int.cbbrowne.com>


> "Joachim Pense" <spam-collector_at_pense-online.de> wrote in message
> news:dkiaao$r43$05$1_at_news.t-online.com...
>> VC:
>>> In MVTSO, a data item in addition to the transaction timestamp
>>> that created the item has a read timestamp. In this model reads
>>> always succeed, and writes are rejected and restarted if their
>>> timestamp is smaller than the data item read timestamp.
>>
>> What does "restarted" mean here? Can that mean "automatically", or
>> does it just mean "rejected and reconsidered by the application if
>> the write should still be done"?
>
> The standard MVTSO model implies automatic restart.

If a legal update is blocked from proceeding, then that's more than close enough to being a "lock" that it surely ought to feel uncomfortable to claim "it's a non-locking model."

-- 
let name="cbbrowne" and tld="gmail.com" in String.concat "@" [name;tld];;
http://linuxdatabases.info/info/slony.html
Rules of the  Evil Overlord #222. "I reserve the  right to execute any
henchmen  who appear  to be  a  little too  intelligent, powerful,  or
devious. However if I do so, I will not at some subsequent point shout
"Why am I surrounded by these incompetent fools?!"
<http://www.eviloverlord.com/>
Received on Sat Nov 05 2005 - 10:05:45 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US