Both are open source databases. This is old debate. Yes no one can expect one database fits all your jobs.
To choose between the two databases, you need to understand whether you need the transaction support of Postgres or the large-text-area support in MySQL.
From the article:
It's interesting that the two databases appear to be converging to meet in the middle somewhere. While MySQL is working on adding transaction support and slowly adding features like subselects, Postgres is making progress in the performance and stability.
It compare two databases using following points:
- SQL standard COMPLIANCE
- DATA INTEGRITY
- SPECIAL server-side FEATURES
- LOCKING and CONCURRENCY SUPPORT
- LARGE OBJECTS etc
A good read (little old too) but don't forget to make some test running before selecting your database.
- 30 Handy Bash Shell Aliases For Linux / Unix / Mac OS X
- Top 30 Nmap Command Examples For Sys/Network Admins
- 25 PHP Security Best Practices For Sys Admins
- 20 Linux System Monitoring Tools Every SysAdmin Should Know
- 20 Linux Server Hardening Security Tips
- Linux: 20 Iptables Examples For New SysAdmins
- Top 20 OpenSSH Server Best Security Practices
- Top 20 Nginx WebServer Best Security Practices
- 20 Examples: Make Sure Unix / Linux Configuration Files Are Free From Syntax Errors
- 15 Greatest Open Source Terminal Applications Of 2012
- My 10 UNIX Command Line Mistakes
- Top 10 Open Source Web-Based Project Management Software
- Top 5 Email Client For Linux, Mac OS X, and Windows Users
- The Novice Guide To Buying A Linux Laptop