Re: Lock-free databases

"Paul" <paul_at_see.my.sig.com> wrote in message news:to2sm11etvv10lalg80moos57v8jh9qolo_at_4ax.com...
>
>
> "-CELKO-" <jcelko212_at_earthlink.net> wrote:
>
>> >> Is there any significant benefit to making a database lock-free? <<
>
>> You have logical concurrency control and optimistic concurrency
>> control. Both methods let you read and write at the same time. And
>> obviosuly, you save the overhead of locking.
>
>
>> Look at Innerbase (aka Firebird) and its performance.
>
>
> Interbase that should be. Firebird is the Open Source project derived
> from when Borland Open Sourced Interbase (but subsequently took it
> back into the fold).
>
> InnoDB - recently purchased by Oracle has a similar mechanism.
>

Both Interbase and InnoDB rely on locking when handling write requests.

>
>
> Paul...
>
>
>
> --
>
> plinehan __at__ yahoo __dot__ __com__
>
> XP Pro, SP 2,
>
> Oracle, 9.2.0.1.0 (Enterprise Ed.)
> Interbase 6.0.1.0;
>
> When asking database related questions, please give other posters
> some clues, like operating system, version of db being used and DDL.
> The exact text and/or number of error messages is useful (!= "it didn't
> work!").
> Thanks.
>
> Furthermore, as a courtesy to those who spend
> time analysing and attempting to help, please
> do not top post.
Received on Sun Nov 06 2005 - 15:28:35 CET