The company that wrote it is a Postgres consulting firm so take it with a grain of salt. Kind of like an AngularJS consulting firm that took thousands of hours

The company that wrote it is a Postgres consulting firm so take it with a grain of salt. Kind of like an AngularJS consulting firm that took thousands of hours to become an expert in Angular writing an article about how horrible they determined ReactJS is after 3 hours with it. Edit: With that said, I've been a mySQL user for years (decades?) and it does have some obvious short comings that PostgreSQL does not. I often times consider switching but the thing is that in 90% of my projects the database engine is not relevant.