You missed the biggest differentiator between the two: licensing. Depending on what you do, your use of MySQL may require a commercial license. Even if not, MySQL Community Edition is licensed under GPLv2 which contains some strict rules and requirements. Postgres is licensed under the PostgreSQL License, which basically says "do whatever you want with it, including embedding it in your product. Your only requirement is to include our license notices.'

Problem with many 'feature, checkmark' comparisons is that they often skip important nuance and depth. postgres's json support blows away anything else in the market because it's directly embedded into the type system, you can do things like, "select json_agg(f) from foo f;" Relating to this comparison, the distinction between performance and speed doesn't make any sense. One of the specific features relating to speed, partial indexes, is in both databases.

I loaded PostgresQL and MySQL (Maria.. too) with half a million selects, insert and updates per hour on an old PC. No tuning, just "apt-get install". MySQL died immediately, Postgres has worked like a charm ever since, I couldn't believe it as processors run on maybe 20% of their capacity (both via JDBC and some Rust connector), magic. I thought the opposite for 30 years, "mysql is lightweight and fast, Postgres is a complicated, object-oriented engine". My employer, the biggest IT environment in a European country, uses Postgres only now for all new projects, slowly migrating Oracle DBs. How stupid we all have been not trusting Postgres?!

As an ex PostgreSQL developer, I can say that it's a completely wrong explanation and hides tons of essential details.

Comparing MySQL to Postgres is like comparing Microsoft Access to Microsoft SQL Server. The first is a sloppy attempt to create a storage system, the latter is a database. One of the happiest days of my technical career was when i moved from MySQL to Postgres. It is so obvious that the core of Postgres is built by people that understands databases, and that the same is not true for MySQL. The learning barriers caused by the strictness of Postgres is paid back in the first week. Just look at the documentation, Postgres is far superior and honest.

Actually the full text capabilities of Mysql are abysmal. In Postgresql using the gin_trgm index is an absurd amount faster then anything accomplishable in mysql. (This creates trigrams, allowing one to do superfast searches on fragments)

Best feature of postgres over mysql that i found is returning results in update queries, very helpful for bulk update use case scenario

The AI has the humor of a software engineer

Very interesting. I am very impressed at your skill of being able to write neatly in mirror form.

Man, it's so strange to be searching for info on PostgreSQL and stumble across Martin "Homebrew Challenge" Keen.

What is the difference between performance and speed ?

You forgot the mysql h.a. with innodb cluster and mysqlbackup for doing online compress backups

In fact, i don't see too much usage of mysql except if there is any php code. As i see: javascript developers often prefer mongodb, golang developers prefers postgres and rust developers prefer postgres or sqlite. Usually usage of mysql are limited with php.

Wait... I think I missing your explanations about speed in Mysql vs performance in Postgresql

You explained very good thank you so much. BTW the final joke was really awkward.

postgres is my choice for all kind of small projects aswell, runs great on even the oldes raspi etc..

What impresses me the most is how easily he handwrites in mirror.

Just remember CAP theorm. Most of your db related choice will start to make sense. Apps do scale, and data structures do change over time. What matters is how well you manage it and organise it for smooth transitions between these tools :)

I recently had to choose between the two. We went with postgres because citus is kept up to date with postgres, but vitess is very out of date and missing many features of modern mysql, including some features that were important for us. I wouldn't really say mysql was any easier to develop with etc though. There are a few differences like citext extension vs case insensitive collations but not really had any problems with it.

Remember that MySQL speed is very dependent on the storage engine used. Myisam is very fast if you don't need transactions or acid compliance. If you need transactions and rollback and triggers, then the storage engine you need will remove the speed benefit.

The major difference to me is: MySQL installed successfully. PostgreSQL keeps showing errors and unusable.

Always love to see the impassioned debates generated by software paradigm comparisons.

How that glass blackboard works and mirrored?

I have used both for many years, among others. I agree that MySQL is quicker and easier to get started and use. MySQL is also very fast at large transactional databases but not overly complex ones. PostgreSQL is far more featureful and deals much better with complexity. For example, you can embed a variety of languages for stored procedures. Also, PostgreSQL has much broader capabilities of applying constraints and many other things. PostgreSQL scales out to multiple peer servers for vastly faster and larger data storage, as where MySQL only supports master-slave replication. Overall, MySQL is more featureful than SQL Server, is fast, and scale up pretty well, but not anywhere near PostgreSQL. MySQL's main strength, though, is that it's easier to get up and running and smoother to develop for. And for most web applications, that's really what matters more. For comprehensive enterprise data processing, what PostgreSQL has is what matters more.

Guys, the thumbnail has the name wrong. it is not Postgre it is Postgres or PostgreSQL

Most if not all web hosting companies come with MySQL installed. That in itself is a huge relief…you really don’t want to keep installing and updating your database software

MVCC is used by both, PostgreSQL and for example InnoDB storage engine for MySQL.

You are an IbM worker that is not talking about in4mix or db2 all day!! You are a shiny unicorn.

Shoutout to this man for writing backwards

Had to use Postgresql after 30 years of Oracle experience. Was like time traveling back to the end of the 90s. Lack of features in sql, no parallel queries, not able to scale horizontally (RAC). Miss it.

Really odd comparison. Where is MySQL faster than PostgreSQL? I remember those comparisons 15 years ago, but PostgreSQL isn't difficult to use. I would say that it can be used everything MySQL is used for, but can also be used for far more complex, serious and advanced things than MySQL.

We use postgresql for the power of relational and flexibility of no schema all in one platform by putting gin indexes on jsonb fields.

I love Supabase, which is a BAAS based on Postgres with amazing free quota and visual interface.

Elephants are cooler than dolphins

i was woundering why the video was so bad for 500k subs.. then i realized that its from ibm

They should make a video on how they make their videos!! 🙂

I've worked with both for a couple years and I think they are both very easy to setup (a few hours) using modern technologies like Docker

I love IBM pls hire me

I flip between both of them for different projects... and to be honest, I've never had a need for the "Object" part of postgres... I/we use it in a traditional RDMS way. You know what RDMS I wouldn't use for any of my projects? --DB2. And I used DB2 for 14 years on z/OS and I'd not touch it with a 10 foot pole on any other platform.

For me, personally, the fact that Postgres supports transactional DDL is a big advantage. You can alter columns, create tables, drop tables, migrate data to them, and ROLLBACK if you messed up. MySQL doesn't support this (AFAIK), nor does MsSQL. Maybe Oracle, or IBM DB2 does (haven't checked).

I worked with both over a decade and MySQL ist the PHP of the Databases. I do not know why everyone says MySQL is easier to use because it lacls so many features, it encourages bad habits. Explain is a joke and sometimes gives wrong numbers. There are obsure bugs for example: An developer accidentally created an cte with the same name as an table which segfault the server process. When I came to my current employer I introduced them to postgres und EVERY developer was happy with the change because so many problems suddenly disappeared. The type system an the ability to use arrays, composote type, hstores etc. alone makes it so much easier and faster. Apart from wordpress MySQL is a nogo for us.

what about MariaDB, with Galera Cluster?

Thanks for this. For the newbies mentioning MariaDB in relation would have been a nice touch.

Me, a person with adhd, just realized I missed most of this video because I was enamored with how this guy is so good at writing backwards...

Facebook , KZfaq, Google and so forth using mysql for their heavy load server side apps.

I think the only thing that I've ever missed in mySQL was recursive queries.... other than that, I love things like delete and updates using inner joins. Postgres's biggest selling point to me are the modules such as UUID and geospacial data. That's my point of view as a developer but I know a lot of people who would much rather rely on OracleDB

How's your transactional DDL statements going MySQL? There's never been a good reason to use MySQL over Postgres. Having used Postgres on and off since the 1990's, and giggled at MySQLs not really a database DNA, and all the problems that has caused. Friends don't let friends use MySQL.

Start with entity-relationship modelling - that way you understand what the hell you are trying to do. If I can, I'll use Postgres every time. If not, you maybe can get along with MySQL. As the old joke goes, if your only tool is a hammer, all the problems look like nails. (Oh, and there are FOSS tools to translate ER models into SQL, at least to 3rd normal form, which gives you some security. Or just use posiit noyes on a while board. It all helps to think first)

That was a good explanation

I think this is not a very useful description. Saying "PostgreSQL is for OLTP and MySQL is for Web" and saying one scallable and fast and the other isn't, is a massive oversimplification. You can definitely use PostgreSQL for web applications without it being an issue, and you'd need to scale it very, very far before you start to run into data ingestion issues you can't easily engineer yourself out of. And MySQL isn't just "fast" its fast under specific circumstances, and slower in others. Without specific cases and specific measurements its not a useful discussion. I say this as someone who's worked with either database system for things running on a national scale.

thank you a lot, Martin!

hm...can you make some study cases to prove your meaning ?

wow this guys is writing in mirror inverted fashion. mind blowing

It's unclear why MySql is `easy to use` but Postgres doesn't....

Thank yu i also use postgres for my enterprice application

He writes backwards. What a crazy feature of a man

Oh -- I think you read the punchline to the joke wrong. The real punchline is "This is the only developer that wanted to use MySQL -- all the others left."

I think you are mis informed… the main differences depending on version is pgsql has more SQL features then MySQL like window functions etc… but when it comes to stability and performance MySQL has a better story with galeria cluster and it’s many replica options…

How does his drawing thing work? I'm guessing he's not actually writing everything in reverse

Thank you for this quick and fun comparison video

what about IBM's own RDBMS DB2 vs postgreSQL and mySQL?

Postgresequel and JaiSON

...showed HIM, not HER 😂

I worked for IBM for Years why not recommend DB2

How is *speed* different from *performance* in this context? Also, saying that MySQL is great at web applications is not a feature but a result of circumstance. People used it in that way just because!

Captions at 3:00 say "that enables the simultaneous occurrence of RIGHT [emphasis added] operations and reads. And there's also business", when it should say "that enable the simultaneous occurrence of WRITE [emphasis added] operations and reads. And there's also business". Captions at 4:19 say "and running and get started. And that really goes to my next point, which is speed. So FAR, [emphasis added]", when it should say "and running and get started. And that really goes to my next point, which is speed. So FOR, [emphasis added]".

But I still like the Mysql .

The biggest difference to note about MySQL is it is the only dbms I know of that allows changing the underlying storage engine. This is a underutilized feature, but a powerful one, as it allows you to highly optimize your database for your specific application. You can have everything from a Transactional database (innodb) to a simple one (MyISAM) and even memory, graph or columnstore database, even nosql style etc…You can even create your own custom storage engine completely from scratch and if it is really good people will pay you for it. There are lots of commercial storage engines as well as the built-in ones. There is also MariaDB which should always be mentioned alongside MySQL since it is newer and has more modern built in storage engines and switching to it is easy since it is a drop in replacement for MySQL. It also adds various optimizations and improvements and features.

The problem with this video is that it basically chooses very similar terms for each side giving what seems like the same checkmark for both. I mean it would be hopeful to sort of explain why, like why is complex multi-type queries better in Postgres, I’ve certainly done those in mysql and never noticed any issue. Mysql has clustering which gives high availability like Postgres. As you state at the beginning they are extremely similar. Yes there are small features that work better for one need vs another, and with modern ORMs it may not even be noticible by a developer. To me it’s which one does your organization have the most experience with?

Actually I didn't understand difference between performance and speed. Are they different thing?

MySQL is not scalable that’s why nosql like mongodb (read scalable) and Cassandra (read/write scalable) exists. Unless you use Vitess or Citus. This list of of differences is incorrect with regards to the latest version of each. For example some of the big differences are stored procedures, data types, licenses, connect limits.

This topic deserves more than a 6 min video. It's very nuanced and the choice should not only be made while considering only these few points. There are counter points to be made on both sides depending on workload. Not a great video in my opinion.

Thanks for comparison! But JSON pronunciation made me squirm :)

pgvector on PostgreSQL

I have never heard it pronounced "Jiy-son" 😂 I've always pronounced JSON as "Jason"

Wait... you're the homebrewer I follow!

Just use Postgres for everything. Lolololololol

I agree with wadesworld, you should have started with the licensing aspects of these databases. The rest is totally irrelevant between these products.

"Master Inventor" everybody creating nonsensical titles for themselves

How does he write backwards so quickly and accurately?

Another IT guy brewing a beer 😂❤️👍

Weird how I know this guy as a homebrew guy and the database guy

Noone: Me: Are you bloody writing in mirror?

Incredible how easy he can write mirrored text 😲

MySQL was really really cool ... right up until they were acquired by Oracle. RIP MySQL.

Could you prepare video stream about CDC transactional replications in PostgreSQL .

This may seem like a weird question, but are you the same guy who produces the Homebrew Challenge Channel on KZfaq?

3:20 what do you mean with multiple datatype support? isn't this a basic thing in any DB?

this is great video thank you

Wuuuut I didn't know you're also a fellow programmer, fellow brewer

may I ask : If I created a Postpress database with a username and password on my computer, it can only be opened with this name and password when I migrate it.

If they were relational that would mean that they organize data into relations (that can be depicted as tables but that are not actually tables) that can be operated on using relational algebra/calculi (closed over relations) on which SQL was inspired although it does not adhere to it by many reasons, right?

sooo just use postgresql. i don't like this argument of "ease of use". you need to know SQL in both. if you are not a DB admin, you just write apps on top of DBs, you won't even touch the hard parts - and where you do, you'll be glad to have the one that can do it all. If you are DB admin, then .. what "ease of use" means anyway, since you are the supposed guru?

If anyone can, please inform me about the tools(+equipment) used to make the above video. I tried searching for it but I could not find it. I am really impressed by the quality of this youtube video. Thanks in advance.

thank you alot really helpful i kinda got the humor😂

Ok the world need to understand that we use the letters for a reason. If I hear sequel one more time, I think I'll snap.

How he is writing backwards

That was a really bad joke

i will choose MariaDB

You also missed a very big issue: SQL is SQL. Regardless of mysql or postgres or DB/2, if you don't know how you will query (that's the "Q" in the name") you'll suck with any option. So yes, working with SQL/DS and with nearly anything having a "Q" in their name, what you want to query and how you want to query is the key to performance & storage. Just my 2 cents. :)