MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:Jeremy Smith Date:March 3 2004 7:46pm
Subject:RE: PgSQL vs MySQL
View as plain text  
I have an extrememly query heavy site that I tried to switch from MySQL to
PgSQL.  And after spending literally a week reconfiguring thousands of
queries and rewriting code, I finally had the pgSQL version of the site
live, but when I had even a trickle of users on the site it was HORRENDOUSLY
slow.  Now, if I had optimized my code and my queries for another 3 weeks, I
may have had something that was usable.  But I will take the speed of MySQL
and live without some of the niceties of PgSQL.


-----Original Message-----
From: David Griffiths [mailto:dgriffiths@stripped]
Sent: Wednesday, March 03, 2004 1:28 PM
To:; Mark Warner; mysql@stripped
Subject: Re: PgSQL vs MySQL

As a DBA and someone who has worked both with PostgresQL and MySQL, I think
I can answer this knowingly.

First, MySQL is significantly faster than PostgresQL and Oracle.

Second, MySQL is also a simpler database to set up and configure.

Third, the documentation is better, and there are far more third party books
out there.

Fourth, MySQL has a more impressive list of customers. Yes, there are some
large PostgresQL customers (the .org domain system?), but none like Yahoo
and Slashdot.

MySQL does not have triggers, stored procedures or views yet. Sub-selects
should be out in six months.

After fighting with PostgresQL to try to get it to use indexes, rewriting
tonnes of queries, and still getting poor performance, I gave up on it. I
prefer MySQL with InnoDB.

Some of the gotcha's are valid, and others can be found in any database.
Forewarned is forearmed.


----- Original Message -----
From: <>
To: "Mark Warner" <hammerhed@stripped>; <mysql@stripped>
Sent: Wednesday, March 03, 2004 6:51 AM
Subject: Re: PgSQL vs MySQL

> > What advantages, besides ease of setup, does MySQL hold over PostgreSQL?
> > It would seem, to me, that the two are close competitors (both in
> > quality, and performance).
> Are you sure about quality?  Check out:
> You can check out postgresql's on the same site but they are significally
less critical.   After reviewing this and talking to some other people i'm
switching over to postgresql.   I'm sure there is a place with mysql but I
don't think i'd trust it for anything critical unless you very confident
your developers know what they are doing.
> --
> MySQL General Mailing List
> For list archives:
> To unsubscribe:

PgSQL vs MySQLMark Warner3 Mar
Re: PgSQL vs MySQLdavid.best3 Mar
  • Re: PgSQL vs MySQLMark Warner3 Mar
    • Re: PgSQL vs MySQLCurtis Maurand3 Mar
      • Re: PgSQL vs MySQLRay3 Mar
      • Re: PgSQL vs MySQLMichael Stassen3 Mar
        • Re: PgSQL vs MySQLKevin Williams3 Mar
        • Re: PgSQL vs MySQLCurtis Maurand3 Mar
  • Re: PgSQL vs MySQLDavid Griffiths3 Mar
    • RE: PgSQL vs MySQLJames Kelty3 Mar
    • RE: PgSQL vs MySQLJeremy Smith3 Mar
      • Re: PgSQL vs MySQLKaarel13 Mar
  • Re: PgSQL vs MySQLKaren Abgarian3 Mar
  • Re: PgSQL vs MySQLDavid Griffiths3 Mar
    • Re: PgSQL vs MySQLMark Warner3 Mar
Re: PgSQL vs MySQLEric @ Zomething3 Mar
  • Re: PgSQL vs MySQLMartijn Tonies3 Mar
Re: PgSQL vs MySQLDavid Griffiths3 Mar
Re: PgSQL vs MySQLJeremy Zawodny3 Mar