Re: question about concurrency

From: Ang <angela_at_angelascott.co.uk>
Date: Mon, 19 Nov 2001 20:45:26 -0000
Message-ID: <9tbr1g$d20$1_at_uranium.btinternet.com>

Concurrency addresses how severel users can update a database at once. You need to look at things like 2 phase comit protocol and locking. "Ed prochak" <ed.prochak_at_alltel.com> wrote in message news:e51b160.0111161259.297b0841_at_posting.google.com...
> tongli_at_unagi.cis.upenn.edu (Tong Li) wrote in message
news:<9s24pp$54$1_at_netnews.upenn.edu>...
> > Hello there,
> > I have question about transaction concurrency.
> > The concurrency is more important when data be fetched from (slow) disk
or
> > when transactions are long, but I just wonder if it nessecery when the
data
> > is in memory and transactions are very short?
> > Thanks in advance,
> > Tina
>
> So you think that having data in fast RAM with a fast CPU is going to
> save you from transaction problems?
>
> Think about busy systems (i.e., many transactions happening often).
>
> Ed Prochak
Received on Mon Nov 19 2001 - 21:45:26 CET

This message: [ Message body ]
Next message: Colin Kinsella: "Re: Help with basic normalization (revised)"
Previous message: David Cressey: "Re: Designing RDBMSs?"
Maybe in reply to: Tong Li: "question about concurrency"
In reply to Ed prochak: "Re: question about concurrency"
Next in thread: Colin Kinsella: "Re: Help with basic normalization (revised)"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message