A common request is "Which database is better? PostgreSQL or DatabaseX"

Of course, the underlying problem is that most requestors don't post their definition of what constitutes "Better."

I DO know that almost every application has different database requirements, and a feature that is of little or no consequence to ApplicationA may be of DIRE importance to ApplicationB.

The plain and simple fact is that you can apply (with varying levels of work on your part) almost any of the serious database contenders in most applications, and make it work. However, some database ARE better suited for specific applications than are others, and the attached links try to clarify this.

Note: I try not to get involved in these sorts of discussions, as they tend to quickly break down into fervent, almost religious arguments as to why "DatabaseA is better than DatabaseB."

That being said, here are the current links...

• *** Open Source Database Feature Comparison Matrix ***
• PostgreSQL vs. MySQL: Building better databases
• PostgreSQL vs MySQL: Which is better?
• PostgreSQL vs. MySQL vs. Commercial Databases: It's All About What You Need
• PostgreSQL: The Industrial-Strength DB with the Tricky Name Vs. MySQL: A Freebie DB That Runs Like the Expensive Brands
• PostgreSQL vs "Larry 8i" (Note: Until it was recently struck down by the U.S. Supreme Court, Oracle's licensing agreement expressly forbade the publishing of bookmark results.)
• Open Source Databases: As The Tables Turn
• Feedlounge Now Running PostgreSQL
• Tweakers.Net Testing
• 50 things to know before migrating from Oracle [PostgreSQL] to MySQL
• PostgreSQL vs. MySQL - A Comparison of Enterprise Suitability