Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Stop using MySQL in 2026, it is not true open source

optimizedbyotto.com

Post reply on HN
Print view View original

31–37 of 37 posts

Re: Stop using MySQL in 2026, it is not true open source

#31

Post by 1over137 »

mlinster wrote: post #18
1over137 wrote: post #16

Earlier quoted context omitted.

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 c…

I'll read up on that, thanks!

Re: Stop using MySQL in 2026, it is not true open source

#33

Post by tzs »

gnabgib wrote: post #15
dfajgljsldkjag wrote: post #2

The 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

That site is not measuring usage. By usage SQLite would be way above all the others. There are more SQLite deployments in use than all the others combined.

Re: Stop using MySQL in 2026, it is not true open source

#34

Post by mannyv »

bitbasher wrote: post #21

Why would anyone use MySQL over Postgres in 2026?

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.

Re: Stop using MySQL in 2026, it is not true open source

#35

Post by frje1400 »

antonvs wrote: post #6

Who's still using MySQL on the back end? Most Linux distributions come with MariaDB. Is it Windows servers?

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.

Re: Stop using MySQL in 2026, it is not true open source

#36

Post by afiori »

captain_coffee wrote: post #14
1over137 wrote: post #11

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?

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

What happens if there are cycles of FK constraints between rows?

Re: Stop using MySQL in 2026, it is not true open source

#37

Post by wink »

frje1400 wrote: post #35
antonvs wrote: post #6

Who's still using MySQL on the back end? Most Linux distributions come with MariaDB. Is it Windows servers?

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.

> Do you think a mature company just migrates to a different database

You are right if you look at the current state of how MariaDB and MySQL diverged. But if you migrated right at the time of the split or close to, they were not different in a meaningful way.

> unless it is absolutely necessary

Staying free of Oracle is often deemed absolutely necessary.

Post reply on HN