Re: RE: Why is there so much MySQL bashing??? - Mailing list pgsql-general

From Lamar Owen
Subject Re: RE: Why is there so much MySQL bashing???
Date
Msg-id 3A65C71E.B7471131@wgcr.org
Whole thread Raw
In response to RE: Why is there so much MySQL bashing???  (Philip Hallstrom <philip@adhesivemedia.com>)
List pgsql-general
Philip Hallstrom wrote:
>
> You're right of course, I should have left that out... but my point is
> still valid.

Pointing out the serious limitations in MySQL is not, IMHO, bashing.

MySQL currently has serious limitations for many RDBMS uses.

Concurrent performance under industry-standard benchmarks in one
indicator.  I my previous conversations with Monty, anytime I brought up
the subject of multiuser benchmarks, he consistently stated that the
single-user case was more important, as that's how the current (as of
the last time I looked) MySQL 'benchmarks' are structured.

Concurrent benchmarking, with a real-world mix of queries (such as AS3AP
and TPC-C), is far more useful to those who are using an RDBMS for more
than just a web backend.  Although, it is a useful average indicator of
web backend performance as well.

And I have to note that SourceForge switched for performance reasons.

Seems there was a great deal of Postgres-bashing from the MySQL side not
long ago.....
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

pgsql-general by date:

Previous
From: "Gordan Bobic"
Date:
Subject: Using max() MUCH slower in v7.1
Next
From: Tom Lane
Date:
Subject: Re: Re: Bug#82029: Postgres installing (fwd)