Re: Indexes and Logical design

From: vc <>
Date: 12 Sep 2005 05:44:43 -0700
Message-ID: <>

Christopher Browne wrote:
> > Besides, sequential retrieval for a read/write transaction requires locks on
> > the entire table, which results in coarser locks and degraded concurrency.
> Not necessarily; alternative mechanisms exist, and are actively used.
> Pretty well any of the database systems still undergoing active
> development offer some variation of MultiVersion Concurrency Control
> (MVCC) where updates lead to creating new versions of tuples, which
> allows the reads, at least, to not require any locks...

Sorry, regardings locks, I should have made it clear that I was answering in the context of Rdb/VMS that does not have MVCC. The little known Rdb/ELN, of which Interbase is a cousin, does implement MVCC and your argument holds there.

> --
> (reverse (concatenate 'string "moc.liamg" "_at_" "enworbbc"))
> If we were meant to fly, we wouldn't keep losing our luggage.
Received on Mon Sep 12 2005 - 14:44:43 CEST

Original text of this message