Obviously I love learning new things, but I've just never felt inclined to try it out, whereas I'm always jumping between other languages and frameworks within them. Not sure why that is.
You don’t realize how limited you are until you really get into all the additional capabilities that PG brings…and then have them unavailable.
> MySQL is a pretty poor database, and you should strongly consider using Postgres instead.
https://web.archive.org/web/20220104181634/https://blog.sess...
I find it pretty interesting that for the DB write-intensive portion[0] of the TechEmpower web framework benchmarks, you must go further than entry 150 (sorted by most requests-per-second) to find MySQL used, compared to PostgreSQL or Mongo. For the DB read-intensive portion[1], only 15 of the top 100 use MySQL (the rest in that bracket use PostgreSQL), and the first entry there comes in at number 44. Important: if you examine the entries, you'll find that some of the frameworks have multiple listings for different configurations, including the use of MySQL vs PostgreSQL (in other words: same framework, but only the DB is different, in the same test).
[0] https://www.techempower.com/benchmarks/#section=data-r20&hw=...
[1] https://www.techempower.com/benchmarks/#section=data-r20&hw=...
I’d highly recommend to try PostgreSQL yourself and learn it’s config, permissions, replication, administration and querying capabilities. You’ll appreciate PostgreSQL’s casting with :: for example. If you had to start from scratch, you’ll be better informed about PostgreSQL and can include it in your selection process.
When we used MySQL, we loved the ease of replication and tooling such as Monyog/Webyog/Workbench. When we used PostgreSQL, we loved the query optimizer and JSON functions.
I would not choose MySQL over Postgresql because of this, never mind all the other features.
MySQL clustering and operations tooling seems much better. No vacuums to worry about