6 ms·

Why you'd use MySQL rather than PostgreSQL in 2016 baffles me unless you're supporting a legacy application, I feel your pain.

• greyskull 10y ago
  One interesting case with Uber: https://eng.uber.com/mysql-migration/ https://eng.uber.com/mysql-migration/
  • ch4s3 10y ago
    Most of us aren't doing millions of writes per second though.
  • minimaxir 10y ago
    An extreme edge case is not a counterargument.
  • debaserab2 10y ago
    That's not that interesting to most of us. That's a huge edge case that I've seen used as fodder in every MySQL vs Postgres argument on HN since it's come up since that blog article was published.
  • glogla 10y ago
    That shows MySQL can be used as a base for building your own key-value store on. It doesn't say anything about it being reasonable (or even good) relational database.
• soared 10y ago
  I'd argue that the majority of people are supporting legacy rather than building something new, or something that has been built in the past couple years.
  • comboy 10y ago
    New? Postgres has been around for 20 years.
    • Cshelton 10y ago
      Actually longer than that. It effectively is what Ingres was a long time ago before Oracle basically killed them off. I believe Ingres was a product of some IBM people? Way way ahead of its time.
• cyberferret 10y ago
  As someone who has used MySQL with absolutely no problems on over 100 projects over the past 20 years, I really don't get the hate I see for it on HN and other places. I've never used Postgres so cannot comment on that, but unless someone can show me that MySQL kills kittens with every query and Postgres moves us one step closer to a cure for cancer with every SELECT, then I'm just going to carry on over here in my corner...
  • gbog 10y ago
    > unless someone can show me Why no. If you do not get why PostgreSQL is so much better than MySQL after reading so many people telling you otherwise, I guess I will not spend time on this task. There are some people prefering PHP over Python or Golang, too. Just a hint: if you did not try PostgreSQL, just maybe give it a try? And yes, MySQL kills kittens (i.e. potentially silently truncates data) at every UPDATE it receives.
    • marklgr 10y ago
      > I guess I will not spend time on this task. Then why do you comment at all? Your post brings nothing to the discussion but appeals to popularity and shaming gp.
    • cyberferret 10y ago
      Well, I'll give you credit for going that little bit further than the post I was responding to. At least you gave a hint as to ONE issue that MySQL can have (which, by the way, I have never come across in the millions or so UPDATES that my projects have done over the years). A link to a discussion about the problem would have been handy, but, oh well. And I actually did try PostgreSQL once or twice many years ago. If I remember correctly, it was for a project that required full text search capability, and I had no end of trouble trying to configure and optimise PostgreSQL to do it back then, and simply reverted back to MySQL which worked out of the box. Or possibly I even went to SQLite with FTS3 back then to get it to work. I, like most developers would rather be creative on my code rather than fight my tools.
    • conorh 10y ago