Given all the excitement around open-source databases, now is a good time to take a look at which of the two most popular options—MySQL and PostgreSQL—is a "better" choice. Of course, theres no quicker way to get third-degree burns from a flame war than to imply that one database is "best." Each has their own set of devotees, and both groups are vocal and devoted, and both can give ample reasons why their choice is the right choice.
As pointed out (in a great article thats full of details concerning the relative strengths of the two databases on the basis of features, support, ease of use, stability, speed, existing skills and licensing) by Ian Gilfillan in Database Journal, "best" is a loaded term. "What is best in one situation is not best in another," Gilfillan writes. "Therefore, the correct answer would be neither is best, and both have their place."
Starting with an objective mind, it can be illustrative to look at what opinionated people have to say both for and against both of the databases. In addition to checking out zines like Database Journal, Ive been haunting Slashdot forums and the blog of MySQL expert Jeremy Zawodny to get a sense of who likes which open-source database for what reasons. Heres a sampling of what Im gleaning: