But as most will tell you in any db forum - there's rarely a simple "product x is faster" when it comes to databases, it depends how you're using it. Any benefits mysql has in some simple usage situations rarely outweighs all the other feature, technical and reliability benefits of postgres. It generally only would make sense if you had some very specific performance requirements where it made a difference for you - and even then, not for all of your data.Īnd in that case maybe that high-throughput task shouldn't be being performed in SQL to begin with.įrom what I've read (a lot), these days the performance between postgres and mysql+innodb is pretty much the same on average. I would never use MyISAM as a primary datastore these days. Using InnoDB (supports ACID), the performance differences to postgres seem to fade away. If you're reading comparisons that were written or reporting on stuff built 5+ years ago, then quite a lot of them are talking about MyISAM (no acid) on mysql, and usually with very simple schemas and queries. Most of what you read on the web is old, and then you see a lot of forum posts repeating that info later on too. In my small research i have found that MySQL is faster than Postgres because Postgres supports ACID. Very unlikely I'll ever start any new projects with mysql from now on. I used mysql exclusively for about 16 years and only starting using postgres last year on my new projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |