RE: [GENERAL] TODO list elements

Hiroshi Inoue <inoue@tpf.co.jp>

From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: "Vadim Mikheev" <vadim@krs.ru>
Cc: "The Hermit Hacker" <scrappy@hub.org>, <pgsql-general@postgreSQL.org>
Date: 1998-12-14T09:13:14Z
Lists: pgsql-hackers
> -----Original Message-----
> From: root@dune.krs.ru [mailto:root@dune.krs.ru]On Behalf Of Vadim
> Mikheev
> Sent: Monday, December 14, 1998 5:03 PM
> To: Hiroshi Inoue
> Cc: The Hermit Hacker; pgsql-general@postgreSQL.org
> Subject: Re: [GENERAL] TODO list elements
> 
> 
> Hiroshi Inoue wrote:
> > 
> > > And note - this will be not row level locking, but
> > > multi-version concurrency control.
> > >
> > 
> > What does it mean ?
> > LLL in 6.5 doesn't include row level locking ?
> 
> One systems (Informix, Sybase) use locking for concurrency control, 
> another ones (Oracle, Interbase) use multi-versioning for this. 
> I'm implementing multi-version concurrency control.
>

My words might be obscure.

What I meant was
 
 How writers block other writers in LLL ?

Certainly readers block no writers(readers) in LLL.
But writers block no writers or the same-row writers or the same-table 
writers ?

Currently writers block the same-table writers(readers also) ?

Thanks.

Hiroshi Inoue
Inoue@tpf.co.jp