You are right. MySQL will be used for years and years. And it is getting better every day.
But MySQL is still behind Postgres in features and reliability. I have being bitten by MySQL shortcomings for a year. Last month was the limit of max 64 indexes per table. Before that it was the dozens of stupid limitations in the procedures and functions. Before that it was some stupid bug that only happens in master-master replication. I can go on for days ranting about MySQL.
Think SVN vs Git. SVN can get better everyday and it does get better, but incremental upgrades will never convert SVN to Git. You scale MySQL by putting Memcached in front of it. But this makes MySQL a fast read-only DB. You can't scale MySQL in a OLTP setup.
Postgres had some performance and scalability issues about 3 or 4 years ago. But the foundations were solid. Now Postgres has fixed those issues and the foundations are better than ever. You can scale Postgres in a OLTP setup and it will eat MySQL lunch every time.
But MySQL is still behind Postgres in features and reliability. I have being bitten by MySQL shortcomings for a year. Last month was the limit of max 64 indexes per table. Before that it was the dozens of stupid limitations in the procedures and functions. Before that it was some stupid bug that only happens in master-master replication. I can go on for days ranting about MySQL.
Think SVN vs Git. SVN can get better everyday and it does get better, but incremental upgrades will never convert SVN to Git. You scale MySQL by putting Memcached in front of it. But this makes MySQL a fast read-only DB. You can't scale MySQL in a OLTP setup.
Postgres had some performance and scalability issues about 3 or 4 years ago. But the foundations were solid. Now Postgres has fixed those issues and the foundations are better than ever. You can scale Postgres in a OLTP setup and it will eat MySQL lunch every time.