From: | Christian Fowler <spider(at)viovio(dot)com> |
---|---|
To: | Evilio del Rio <edelrio(at)cmima(dot)csic(dot)es> |
Cc: | postgresql performance list <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Postgres vs. MySQL |
Date: | 2004-11-24 14:57:52 |
Message-ID: | Pine.LNX.4.61.0411240908400.22359@leda.steelsun.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
As for performance, lots of others will probably volunteer tips and
techniques. In my experience, properly written and tuned applications will
show only minor speed differences. I have seen several open-source apps
that "support postgres" but are not well tested on it. Query optimization
can cause orders of magnitude performance differences. It sounds maybe
dspam is in this bucket?
>
> Please, could anyone explain me this difference?
> Is Postgres that bad?
> Is MySQL that good?
> Am I the only one to have observed this behavior?
I made a little chart about these about a year ago:
http://www.tikipro.org/wiki/index.php?page=DatabaseComparison
If speed is what you need, and data integrity / safety is not, then MySQL
may be a good choice. (Aggregate statistics tables and other such
calculated denormalizations).
IMHO, if all you need is dpsam running *now*, then I'd say MySQL might be
good choice. If you ever need to run a DB application where data integrity
is mission critical, then postgres is the top of my list.
[ \ /
[ >X< Christian Fowler | spider AT viovio.com
[ / \ http://www.viovio.com | http://www.tikipro.org
From | Date | Subject | |
---|---|---|---|
Next Message | Alexandre Leclerc | 2004-11-24 15:39:03 | Re: Data type to use for primary key |
Previous Message | Richard Huxton | 2004-11-24 14:27:06 | Re: Postgres vs. MySQL |