Saltar a contenido principal

🧙 This is massive
The Future of MySQL is PostgreSQL:
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.
news.ycombinator.com/item?id=4…
nextgres.com/res/20240419-The-… (edited)

Postgres is on the rise. MySQL is in decline. But there are a helluva lot of MyS... | Hacker News

news.ycombinator.com

reshared this

in reply to tobyhede

Lewis Cowles
Lewis Cowles
• •
the AWS part of it isn't great; and IDK if it is true that Postgres replication is worse than MySQL
in reply to tobyhede

obrhoff
obrhoff
• •
Jonah Harris is the CTO of MariaDB? Does it mean it's dead?
in reply to obrhoff

Andrew (LinuxJedi) Hutchings
Andrew (LinuxJedi) Hutchings
• •
@obrhoff he left as the CTO of MariaDB Plc. No, it is definitely not dead.
Also, the MariaDB Foundation exists to keep MariaDB Server development going. We work with the Plc, but are a completely separate entity.
@obrhoff
in reply to tobyhede

Daniel Casanueva
Daniel Casanueva
• •
Excuse my ignorance, but this all assumes that PostgreSQL is just better than MySQL and that you should use PostgreSQL if given the option. I'm no database expert. Can someone kind explain to me in which way PostgreSQL is better? Is this for all use cases? Thanks.
in reply to Daniel Casanueva

Latte macchiato :blobcoffee: :ablobcat_longlong:
Latte macchiato :blobcoffee: :ablobcat_longlong:
• •

Full ACID compliance, massively more advanced indexes, NoSQL (JSONB) support, stored procedures in multiple languages, more powerful triggers, support for full concurrency on both reads and writes (MVCC), big plug-in ecosystem and more.

Postgres is in my opinion simply the superior choice in everything but the learning curve. It also scales better than MySQL does.

in reply to Latte macchiato :blobcoffee: :ablobcat_longlong:

Latte macchiato :blobcoffee: :ablobcat_longlong:
Latte macchiato :blobcoffee: :ablobcat_longlong:
• •
Oh, not to forget Row Level Security. With something like Supabase you can forego backend code on some applications entirely.
in reply to Latte macchiato :blobcoffee: :ablobcat_longlong:

Mathias Panzenböck
Mathias Panzenböck
• •
@privateger @danielcasanueva And transactional database schema changes! No more wrecked database state after a failed migration! That's a big one for me. (SQLite also supports this.) And then extensions like PostGIS and pgvector are also nice.
@Latte macchiato :blobcoffee: :ablobcat_longlong: @Daniel Casanueva
in reply to Latte macchiato :blobcoffee: :ablobcat_longlong:

Daniel Casanueva
Daniel Casanueva
• •
@privateger Thanks for the answer! It was my understanding that MySQL is also ACID-compliant through InnoDB. This is something important. The most advanced features I'm not sure I will use. However, I'll look a bit more into it and see if it's worth a migration.
@Latte macchiato :blobcoffee: :ablobcat_longlong:
in reply to Daniel Casanueva

Latte macchiato :blobcoffee: :ablobcat_longlong:
Latte macchiato :blobcoffee: :ablobcat_longlong:
• •
InnoDB is ACID compliant, but myISAM isn't. It was the default for a long time and is still used quite often.
in reply to tobyhede

Shane Kerr
Shane Kerr
• •
I had to double check that this wasn't an April 1st post. Amazing!
⇧