Re: [HACKERS] Large databases, performance

From: Andrew Sullivan <andrew(at)libertyrms(dot)info>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: [HACKERS] Large databases, performance
Date: 2002-10-03 21:09:20
Message-ID: 20021003170920.X18497@mail.libertyrms.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-performance pgsql-sql

On Thu, Oct 03, 2002 at 06:51:05PM +0200, Hans-J?rgen Sch?nig wrote:

> In the case of concurrent transactions MySQL does not do as well due to
> very bad locking behavious. PostgreSQL is far better because it does row
> level locking instead of table locking.

It is my understanding that MySQL no longer does this on InnoDB
tables. Whether various bag-on-the-side table types are a good thing
I will leave to others; but there's no reason to go 'round making
claims about old versions of MySQL any more than there is a reason to
continue to talk about PostgreSQL not being crash safe. MySQL has
moved along nearly as quickly as PostgreSQL.

A

--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jean-Luc Lachance 2002-10-03 21:12:02 use [PERF] instead of
Previous Message Ron Johnson 2002-10-03 20:55:35 Re: [HACKERS] Large databases, performance

Browse pgsql-hackers by date

  From Date Subject
Next Message Jean-Luc Lachance 2002-10-03 21:12:02 use [PERF] instead of
Previous Message Bruce Momjian 2002-10-03 21:02:43 Re: CVS checkout errors

Browse pgsql-performance by date

  From Date Subject
Next Message Jean-Luc Lachance 2002-10-03 21:12:02 use [PERF] instead of
Previous Message Ron Johnson 2002-10-03 20:55:35 Re: [HACKERS] Large databases, performance

Browse pgsql-sql by date

  From Date Subject
Next Message Jean-Luc Lachance 2002-10-03 21:12:02 use [PERF] instead of
Previous Message Ron Johnson 2002-10-03 20:55:35 Re: [HACKERS] Large databases, performance