Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] What can we learn from MySQL?

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Tim Conrad" <tim(at)timconrad(dot)org>
Cc: "PostgreSQL advocacy" <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: [HACKERS] What can we learn from MySQL?
Date: 2004-04-27 16:27:39
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB34101ADE4@Herge.rcsinc.local (view raw or flat)
Thread:
Lists: pgsql-advocacy
Correction:
> For the record:
> PostgreSQL currently has row level locking: locks are acquired by
writing
> to the data and released by committing/rolling back a transaction.
What
> makes this different from traditional 'library book model' locking
systems
> is that writers do not block writers, only other readers.  Basically,
the

last sentence is backwards: writers block writers, not readers

Merlin

pgsql-advocacy by date

Next:From: Bruce MomjianDate: 2004-04-27 16:34:12
Subject: Re: [HACKERS] What can we learn from MySQL?
Previous:From: Merlin MoncureDate: 2004-04-27 16:25:10
Subject: Re: [HACKERS] What can we learn from MySQL?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group