The storage engine is one of postgres's weakest points. I hope OrioleDB will eventually give us a more robust and easier to use replacement.

Is there anything in 8.0.x/8.4.x line that isn't present in MariaDb latest?

From my experience, mariadb is about the same as mysql... depending on the queries, it can either be fine, or slow as balls. I'm actually considering switching to pgsql to see if its any better. /shrug

If space constrained and wanting compression, why not do that at the filesystem or block layer if it's not supported in the app?

Author is also being careful with the DB-Engines screen shot, usage of MySQL may be dropping, but it's still number two (below Oracle, above MSSQL - which shows the same curve, above Postgres, far above MariaDB and SQLite) https://db-engines.com/en/ranking_trend

How big of a DB are we talking about? You might need to recreate the whole DB schema / structure manually from scratch in PostgreSQL and then dump the data and load it in PG via standard SQL file exports in the correct table order to avoid failures due to FK constraints. This is a gross oversimplification but you get the gist

It does work, I just used pgloader to migrate a 16 GB database from MySQL 8.4 to PostgreSQL 18 last week (around 700 tables). It's not big, but their problems seem to be with authentication, not database size or functionality.

Have you tried it doing it yourself?

Because it's a zero-maintenance solution that performs well out the box, has excellent analysis tools that are free, and works with no issues.

Postgres is work. Mysql is not. I say this having used mysql, postgres, oracle, sybase, mssql, ingres, rdb, dbase, and other random data stores in production.

Because they started with MySQL and it can be difficult to switch.

I'm pretty sure Facebook is still running it. They've done a migration to 8.0 a couple of years after it came out (it was a massive release).

https://engineering.fb.com/2021/07/22/core-infra/mysql

Obviously lots and lots of companies. Do you think a mature company just migrates to a different database unless it is absolutely necessary? That's a multi year project. I'm at a smaller company (around a 100 devs) and we have easily a dozen different production instances, some small and some larger with many replicas, etc.

New projects get MySQL too because we know it and it works.

MySQL performs well at large scale, and has a very cool and weird storage engine option called MyRocks, that slows read performance but allows demented write rates and compression.

But yes, it is very bad.