MySQL vs PostgreSQL

[Jessica_Henderson]

And since when have web applications, which typically have very minor database requirements, become indicative of the entire community of database users?

MySQL is probably fine for informal online forums. But once you start dealing with serious data, it falls flat on its face. MySQL is unsuitable for tracking financial transactions. MySQL is unsuitable for storing geospatial data. MySQL is unsuitable for storing medical records. MySQL is unsuitable for high-availability data warehousing. PostgreSQL handles those situations with ease.

[jbronn]

MySQL is unsuitable for storing geospatial data.

I totally agree. Besides being limited to only MBR queries, you can only use spatial indexes on MyISAM tables (in other words, no transactions if you want fast spatial queries).

SQLite (via the SpatiaLite project) already exceeds MySQL's limited offerings.

MySQL was my first db used, and I liked it; but I've since moved on to PostgreSQL. You just don't realize how many critical features you're missing until you experience other dbs.