Why does it bother you that I recommend Postgres over MySQL?
All else being equal, for new development, Postgres is the better answer - that is not dogma, it is based on experience gained over 8 years and not without a few late nights of fixing something. My clients with an existing code base run whatever they are currently running.
I don't have an opinion on the use of multiple programming languages, the purpose of a database is to reliably store data that (usually) some other programming language uses or produces. It's the reliable storage part that matters.
"All else being equal, for new development, Postgres is the better answer..."
That's very thinly disguised dogma. Whatever the question, Postgres is the answer.
It doesn't bother me though, I'm used to seeing people choose one camp over the other. I just wanted to point out that I use both for different things and it's served me very well. The MySQL vs Postgres discussion itself is unbelievably boring.
All else being equal, for new development, Postgres is the better answer - that is not dogma, it is based on experience gained over 8 years and not without a few late nights of fixing something. My clients with an existing code base run whatever they are currently running.
I don't have an opinion on the use of multiple programming languages, the purpose of a database is to reliably store data that (usually) some other programming language uses or produces. It's the reliable storage part that matters.
If you want a cartoon caricature of me, replace "Unix" and "computer" with "Postgres" : http://static.tabo.aureal.com.pe/pub/img/dilbert-unix.png