Re: Article on MySQL vs. Postgres - Mailing list pgsql-hackers

From Peter Galbavy
Subject Re: Article on MySQL vs. Postgres
Date
Msg-id 04b701bfe699$6fb7e250$81010a0a@flagtelecom.com
Whole thread Raw
In response to Re: Article on MySQL vs. Postgres  (Benjamin Adida <ben@mit.edu>)
List pgsql-hackers
> Yes I'm sure that PHP was designed to make Postgres look bad. All
> benchmarks are designed to make postgres look bad. All web designers
> build everything in just that special way that makes postgres look bad,
> and they all do it because they're inept and stupid, unlike the small
> crowd of postgres users.

I don't believe that your sarcasm is unwarranted, BUT, and this is a big but
(just like mine :), I have found that the popularity of free software is
sometimes iversly proportional to it's complexity. Complexity in turn
sometimes, but not always, implies that the software has more features and
is better thought out. There are exceptions to this, but it has proven true
for many of the packages I have worked with.

MySQL is used by Linux folks (generalising), probably because the learning
curve is not too steep. And the otherway round for other DB + OS
combinations.

The problem I think that many folk have with printed benchmarks is the
apples to oranges comparisons. To make the comparison look valid, you have
to either reduce or ignore the differences of the fruit and just look at a
limited set of values. In the case of the apples and oranges, "average
diameter" may be valid, while "green-ness" is not. The eater of the fruit
actually wanted to know "which tastes better".

Peter



pgsql-hackers by date:

Previous
From: Tim Perdue
Date:
Subject: Re: Article on MySQL vs. Postgres
Next
From: Thomas Lockhart
Date:
Subject: Re: Article on MySQL vs. Postgres