[jonahharris]

Postgres is on the rise. MySQL is in decline. But there are a helluva lot of MySQL applications out there and developers still building against it. While the industry is moving away from MySQL to Postgres, the only solution for this is traditional migrations, which--let's face it--are manageable from a data standpoint, but a pain in the ass to address with applications.

Today, at Postgres Conference 2024, we introduced a PostgreSQL extension we are developing, which enables MySQL applications to run on PostgreSQL without any code changes by supporting the MySQL wire protocol, SQL syntax, and procedural language. It addresses MySQL's large database performance issues by leveraging PostgreSQL's features, such as enhanced partitioning, analytical queries, parallel query, advanced indexing, and materialized views. The extension also gives MySQL developers access to the comprehensive PostgreSQL extension ecosystem, including columnar storage, vector database functionality, and in-database machine learning, providing additional functionality. I mean, Oracle just released a preview of JavaScript procedural language support in MySQL in 2024, whereas our extension inherits Postgres' PLs, giving MySQL developers access to in-database Python, Rust, JavaScript, et al.

Not only that, but our solution consolidates database management, eliminating the need to run both MySQL and PostgreSQL systems, which is common among 75% of businesses using PostgreSQL. This approach improves productivity and simplifies operations.

Our Alpha will be released in July, Beta in September, and we expect to be GA by EOY. Questions welcomed.

[vivzkestrel]

Stupid question, once upon a time MySQL was considered the gold standard of relational databases. The fact that WAMP literally comes with MySQL installed on every domain registrar should say something but what caused its downfall? Was it the fact that it was acquired by a corporate entity?

[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.