I'm stuck on MySQL because converting to postgres is hard, the tool everyone recommends (pgloader) doesn't work with current MySQL (https://github.com/dimitri/pgloader/issues/782), anyone know another way?
Stop using MySQL in 2026, it is not true open source
11–20 of 37 posts
Re: Stop using MySQL in 2026, it is not true open source
#12From my experience MariaDB is not necessarily better than MySQL. The 8.x line brought many interesting features. I dream on switch to Postgres, and try every year but for my use case MySQL is still superior (100Bi+ rows for large texts, and heavy modified - I´m also space constrained - So I need data compression and the VACUUM are not good.) The percona distribution is very good!
If space constrained and wanting compression, why not do that at the filesystem or block layer if it's not supported in the app?
Re: Stop using MySQL in 2026, it is not true open source
#13I would argue that the reason to stop using it is that is a pretty bad piece of software to begin with, not because it's not "true open source" but hey, whatever floats your boat, right?
Re: Stop using MySQL in 2026, it is not true open source
#14I'm stuck on MySQL because converting to postgres is hard, the tool everyone recommends (pgloader) doesn't work with current MySQL ( https://github.com/dimitri/pgloader/issues/782 ), anyone know another way?
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
Re: Stop using MySQL in 2026, it is not true open source
#15The author is right that usage is dropping, but that really has no bearing on whether or not it is open source. Technologies get replaced all the time regardless of the license they use.
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
Re: Stop using MySQL in 2026, it is not true open source
#16I'm stuck on MySQL because converting to postgres is hard, the tool everyone recommends (pgloader) doesn't work with current MySQL ( https://github.com/dimitri/pgloader/issues/782 ), anyone know another way?
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
In fact I don't get the gist :) but thanks for your reply. All I know about databases is following instructions to set one up as part of a LAMP/FAMP installation.
Re: Stop using MySQL in 2026, it is not true open source
#17[dead]
Re: Stop using MySQL in 2026, it is not true open source
#18Earlier quoted context omitted.
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
In fact I don't get the gist :) but thanks for your reply. All I know about databases is following instructions to set one up as part of a LAMP/FAMP installation.
Unless you use stored procedures in MySQL, recreating the tables and schemas in Postgres should be straightforward. Postgres now offers a 'MySQL Adapter', a.k.a. Foreign Data Wrapper (https://github.com/EnterpriseDB/mysql_fdw), that makes it straightforward to load data from MySQL into Postgres.
I know you mentioned that all you know about databases is following instructions, but maybe the folks at EDB or Percona can give you a hand.
Postgres will be around for a long time, and I think it's pretty obvious that MySQL won't.
Re: Stop using MySQL in 2026, it is not true open source
#19I'm stuck on MySQL because converting to postgres is hard, the tool everyone recommends (pgloader) doesn't work with current MySQL ( https://github.com/dimitri/pgloader/issues/782 ), anyone know another way?
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?
Re: Stop using MySQL in 2026, it is not true open source
#20Oracle's icy touch. It was foretold. :D