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

Re: Large databases, performance

From: "Michael Paesold" <mpaesold(at)gmx(dot)at>
To: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Large databases, performance
Date: 2002-10-04 16:38:21
Message-ID: 01c601c26bc4$73d5f900$4201a8c0@beeblebrox (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackerspgsql-performancepgsql-sql
Andrew Sullivan <andrew(at)libertyrms(dot)info> wrote:

> 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.

Locking and transactions is not fine in MySQL (with InnoDB) though. I tried
to do selects on a table I was concurrently inserting to. In a single thread
I was constantly inserting 1000 rows per transaction. While inserting I did
some random selects on the same table. It often happend that the insert
transactions were aborted due to dead lock problems. There I see the problem
with locking reads.
I like PostgreSQL's MVCC!

Michael Paesold

In response to


pgsql-performance by date

Next:From: Andrew SullivanDate: 2002-10-04 16:44:03
Subject: Re: Comparitive UPDATE speed
Previous:From: Hans-Jürgen SchönigDate: 2002-10-04 16:30:47
Subject: Re: [HACKERS] Large databases, performance

pgsql-hackers by date

Next:From: Oleg BartunovDate: 2002-10-04 16:40:01
Subject: any experience with IA-64
Previous:From: scott.marloweDate: 2002-10-04 16:35:38
Subject: Re: Threaded Sorting

pgsql-sql by date

Next:From: David BloodDate: 2002-10-04 16:46:57
Subject: Pinning a table into memory
Previous:From: Hans-Jürgen SchönigDate: 2002-10-04 16:30:47
Subject: Re: [HACKERS] Large databases, performance

pgsql-general by date

Next:From: Tom LaneDate: 2002-10-04 16:44:48
Subject: Re: pg_restore issue..
Previous:From: BtDate: 2002-10-04 16:35:00
Subject: table linking problem

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