Choosing an Open-Source Database
In the end, it doesn't boil down to MySQL or PostgreSQL being "best"rather, it's a question of which database is best for a given situation, writes Database Center Editor Lisa Vaas.In terms of media coverage, open-source databases are having their day in the sun. The most recent tidbit: While the 500+ respondents to Evans Data Corp.s recent Database Development Survey report that Microsofts SQL Server and Access still predominate, MySQL usage by the group surveyed is growing as fast as dandelions in the spring. The survey showed that respondents use of the open-source database grew more than 30 percent last year, compared with a much more modest 6 percent growth in the use of the two Microsoft databases. With LinuxWorld just around the corner, theres only going to be more hubbub around open-source databasesparticularly given that practically all the big database and database tool vendors will be there, including IBM, Oracle, Microsoft, BMC and Computer Associates. Given all the excitement around open-source databases, now is a good time to take a look at which of the two most popular optionsMySQL and PostgreSQLis 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."