Hacker News new | comments | show | ask | jobs | submit login

MySQL would have languished in MyISAM or broken InnoDB world forever.

Ahem. Not to rain on anyone's parade but in my world InnoDB is still broken.

I maintain quite a few production MySQLs and they blow up with great regularity.

Usually it hits individual tables, sometimes (gladly more rarely since the 5 series) it suddenly feels insecure about the contents of ibdata altogether. And no, it's not the hardware.

Anecdote needed?

Just last week we had to drop/re-create an InnoDB-table in one project because it would not allow to add an index anymore, no matter what we tried. If some MySQL expert around here can shed some light, I'm all ear, the error message was:

   Mysql::Error: Incorrect key file for table 'foo'; try to repair it: CREATE INDEX [...]
Google revealed a handful of familiar sounding bug-reports mentioning column-renames, which the table had indeed undergone, but nothing really helpful, so we resorted to the drop/create sledgehammer.

Gladly that worked. This time. And every time I wonder why people can't just use PostgreSQL, where such issues (believe it or not) simply don't exist.

I couldn't agree more with your last statement, but I was trying to sound unbiased ;)

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact