[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MySQL vs. PostgreSQL
Eli Marmor <marmor@elmar.co.il> writes:
>
> Since most of us are not banks and/or the population registrar and/
> or Slashdot, and none of us serves billions of transactions per
> nano-second, it would be expected that most will use PostgreSQL. In
> addition, PostgreSQL is bundled with some distributions (including
> RedHat). But according to the impression I have, MySQL is much more
> popular, even among people who don't need its amazing performance.
>
> Can you explain this? Can you settle the conflict?
1. Historical issues. MySQL was always hyped as a "web-oriented"
database. Postgres (and later PostgreSQL) was promoted as a general
"poor man's Oracle" RDBMS. Also, MySQL was always quite small
(actual size doesn't matter - it was promoted as a SMALL one).
2. Efficiency considerations. When an ordinary mortal is offered
something which is relatively big, general, and slow vs something
small and up to 10 times as fast, what do you expect this person to
choose?
3. Psychological issues. MySQL is not quite free, so people consider
it to be almost "commercial" software which gives them a warm fuzzy
feeling of being "supported".
> I owe an answer to a customer till tomorrow's morning, so quick
> answers may be preferred...
When I am asked what DB to use I always answer - use the one that fits
you best. If the database is not very big, Web-oriented, and it isn't
supposed to grow much (above 100Mb) in the future, and licensing
scheme fits - use MySQL. Otherwise, if the database is rather large,
SQL starndard(s) compliance matters and various access methods will be
used (Perl, ODBC, JDBC etc), or a strictly GPLed software required -
go for PGSQL.
--
Alexander L. Belikoff
Bloomberg L.P. / BFM Financial Research Ltd.
abel@bfr.co.il