
#Pervasive mysql install
That could be because official install repositories/ISPs have more updated versions of MySQL than PostgreSQL. You would think MySQL would have similar issues, but they seem to have less of that. Vastly different from the PostgreSQL 8 series. People need to be reminded that PostgreSQL 6/7 of the past is
#Pervasive mysql plus
This is a huge plus for many ISPs and we know when many projects start out, they can't afford dedicated boxes so they rely on their ISPs to have these things already installed. As Joshua Drake pointed out in the above article, you can do in-place upgrades with MySQL, but really can't with PostgreSQL. MySQL is an easier install and easier to upgrade.

More work needs to be done there to insure binaries/rpms for latest releases are available for most of the OSes PostgreSQL supports and popular add-ons. Up there with the Yum repository, pre-compiled windows binaries and valiant efforts of people making binaries for Mac, Debian, SUSE available. PostgreSQL has caught up there and is beginning to see the fruits of that labor.


Some of what we are going to say is a bit tongue-in-cheek so please don't take offense. So why do people choose MySQL time and time again over PostgreSQL and why is PostgreSQL sometimes a hard sell? This along with other bug complaints is a moot point. Zack Urlocker of Sun has espoused, the upcoming MySQL 5.1 will have no bugs so perhaps
#Pervasive mysql driver
I won't even recount our frustrations with using their ODBC driver with the MySQL 5.0 incarnations, but that could be ignorance on our part. MySQL's casting behavior is shall we say odd. For example, as Magnus Hagander pointed outĪnd we pointed out in SQL Math Idiosyncracies,
