the most famous difference between MySQL and PostgreSQL is related to your read / write ratios. If you read a lot more than you write, MySQL is usually faster; but if you do a lot of heavy updates for the table, as often as other threads should read, then MySQL's default lock is not the best, and PostgreSQL might be the best performance choice.
IOW, PostgreSQL scales better with respect to writing to DB.
why he usually said that MySQL is best suited for webapps and PostgreSQL is more "enterpriseisey".
Of course, the picture is not so simple:
- InnoDB tables in MySQL have very different performance behavior
- At boot levels, where it is better to block PostgreSQL, they intercept MySQL, other nodes of your platform may be bottlenecks.
- PostgreSQL is more standards-compliant, making it easier to replace later.
in the end, the choice has so many variables that no matter how you go, you will find an important problem that makes it the right choice.
source share