5 ms·
MySQL is like Javascript: Full of bad decisions and footguns. It works perfectly fine, but I don’t see why you’d use it when Postgres exists.
by tormeh 2y ago
MySQL is like Javascript: Full of bad decisions and footguns. It works perfectly fine, but I don’t see why you’d use it when Postgres exists.
- nsonha 2y agomore like PHP, which is funny because they always come in pair, prolly originate from the days of LAMP stack. js is more associated with Mongo, another bad db. Most modern js projects (or any modern project really, except PHP) use Postgres
- a012 2y ago20 years ago LAMP (Linux, Apache, MySQL, PHP) stack ~is~ was the most common combo of the web
- graemep 2y agoNot sure about Apache, but Linux, MySQL and PHP is still the most common combo in terms of number of sites running it. Wordpress alone is enough to establish that.
- nsonha 2y ago> most common combo in terms of number of sites running it. Wordpress... does that claim do anything for anyone? India is the most populated country on earth, so?
- treflop 2y agoIt’s because PHP’s popularity is old and Postgres used to be mid. MySQL was faster and better than Postgres. But Postgres slowly improved and then got better than MySQL while MySQL stagnated. The most basic bugs persisted, basic features never got added and consistency never seemed to be a point of improvement.
- Gud 2y agoSorry but MySQL was not really “better” than Postgres. I never understood back then why MySQL was the default choice for so many people.
- viraptor 2y agoDepends on your workload, immutable tuples and vacuum can hurt a lot. (Although that got much better recently) Also the mad decisions about the query planner which you can't control. Often this doesn't matter, but it's worth being aware.
- CuriouslyC 2y agoOh the contortions I've gone through with the query planner to get it not to do things. Also, if you're using JSONB, long strings or other toast entries, your query plan and your performance will be wildly divorced since the planner doesn't factor in a lot of the toast IO and associated memory management. The lesson for others here is if you have JSONB/long text fields, store them in their own table.