What's better? MySQL or PostgreSQL to scale in a large project?

Question

MySQL

What's better? MySQL or PostgreSQL to scale in a large project?
What is the durability, flexibility and other characteristics of each of the tools?

Answer 1

PostgreSQL is definitely better. In terms of stability, I read that MySQL did not give out all the data from the sample under heavy loads.
PostgreSQL has more advanced SQL and a bunch of different goodies + and scales better.
MySQL is slightly faster in performance.
I used MySQL at first, but PostgreSQL is better

Answer 2

MySQL is simpler, PostgreSQL is more powerful.
MySQL big assumptions by default, PostgreSQL strict out of the box
MySQL loves RAM, PostgreSQL loves CPU
Replication, IMHO, both have synchronous multimaster = portal to Hell.
With frequent deletion of data, PostgreSQL solves, because there is a vacuum mechanism that reduces the size of the database on disk, FPT on MySQL solves the problem partially.
Had sex with both DBs, with PG it's less common but nicer.

Answer 3

Definitely PostgreSQL. I had a project in which there were tables with a million to ten records, MySQL (InnoDB) with default settings sagged a lot in performance. Of course, after reading the manuals for setting up the database server and the database itself, I managed to speed up the work, but the performance level did not reach the PostgreSQL level.
MySQL is well suited for lightly loaded projects, but it is better not to use it in heavy projects. With MariaDB, the situation is similar. And PostgreSQL is more of a competitor to Oracle DB than MySQL.
Although Oracle is behind MySQL, they have no motivation to make this database more performant (why create a competitor to their own product - Oracle DB?).