Why is it said that postgress is better for a more or less serious project than anything else?

Question

PostgreSQL

Good afternoon!
All my life I have worked only with mysql, and there is no particular desire to go anywhere (except for self-development).
However, lately, more and more often I meet people on forums who say this:
"If you are planning a serious project, choose postgres. If you are planning a simple project that will grow into a serious one - again - postgres."
And why?
Why, for example, mysql is worse?
Just ask for answers from practice. Because I read a lot about the technical characteristics, and to be honest, I understood little: muscle is a relational database, postgres is an object relational one. This is all good, but I would like to understand how this will affect the project.
Thank you!

Answer 1

This question is asked about once a week on Toaster, and the internet is full of comparisons. For example, this or this . For me personally, the most important jamb of MySQL is that in 2018 it does not even support the SQL standard of 92 in full. Or here's a bug from a recent question - it doesn't fire a trigger on foreign key actions. And there are just a monstrous number of such jambs. As soon as you go beyond something more complicated select * from some_table, you start swearing at developers every second. And one more fact that has little effect on everyday work, but worthy of mention - when checking the code of several popular RDBs with a static analyzer, MySQL turned out to be in first place by a significant margin in terms of the number of errors!

Answer 2

Not this way.
Serious projects, for example, at the same Google work fine with MySQL
MySQL has less functionality, it's simpler, and therefore faster in many cases.
But the implementation of functionality that is missing in MySQL with a MySQL add-on will cost more in terms of performance than using such functionality already available in PostgreSQL.
As an example, JSONB (I recommend it in PostgreSQL, it works efficiently, allows you to implement schemeless). Not to be confused with JSON (this is an old implementation in PostgreSQL, deprecated).
Watch Oleg Bartunov's speeches on Youtube - he is a PostgreSQL developer and does educational work on some PostgreSQL features.

Answer 3

Because postgres is such a Swiss knife that literally has everything and it works, and the authors are working on development and optimization.
It was only on postgres that I managed to upload data to the table at the speed of the network interface using libpq.

Answer 4

postgres - DBMS, with a kernel that began to be developed when part of the audience was not yet in the project, sponsored by DARPA at Berkeley,
muscle - a wrapper over the DBMS (innodb, myisam, etc), 9 years later, in Sweden, not at the university, was created as a scull wrapper for another jap

Answer 5

I am pleased with the aggregate functions in postgres, which I did not find in mysql