[jonahharris]

Based on conversations with a lot of developers and businesses, a few things happened, I think. First, MySQL hasn’t been keeping pace with Postgres feature wise; second, MySQL isn’t the migrated-to database from Oracle Database or SQL Server, Postgres is - and as companies don’t want to have to manage multiple databases, if their departmental apps all go to Postgres, then it becomes the default development database also. The most important, I think, is the MySQL community and ecosystem. There’s a ton of users and tools, but not much in terms of development or plugins that enhance the server like Postgres has. MySQL is still used heavily for high performance web sites but, aside from that, it’s not great in mixed workload OLTP or OLAP, and large OLAP workloads really need something like HeatWave. TiDB and Vitess are great for scale out OLTP when normal single server MySQL gets overwhelmed.