postgre used to be superior due to the fact that it had a ton of features that mysql didn't have. now they're approximately even, although postgre does still have more robust features.
mysql, i believe, performs better in most situations and configurations. in the black art of performance tweaking, you can tweak them both down pretty well, but mysql still stays better performing (edited to add:) in general. YMMV based on the needs of your app.
In terms of stored procedure language and locking strategy Postgres is still light-years ahead of MySQL. You can almost think of Postgres as the free Oracle. Going feature-for-feature by introduction date, MySQL is 10-15 years behind.
Comments
postgre used to be superior due to the fact that it had a ton of features that mysql didn't have. now they're approximately even, although postgre does still have more robust features.
mysql, i believe, performs better in most situations and configurations. in the black art of performance tweaking, you can tweak them both down pretty well, but mysql still stays better performing (edited to add:) in general. YMMV based on the needs of your app.
In terms of stored procedure language and locking strategy Postgres is still light-years ahead of MySQL. You can almost think of Postgres as the free Oracle. Going feature-for-feature by introduction date, MySQL is 10-15 years behind.
... it depends ...
yeah, there's no doubt about the fact that its situational.
just like picking a language