4 ms·
>Typically PHP stuff where the paid developers hyperoptimise for MySQL That's quite true. My experience with MySQL comes from working with company intranet i
by proveanegative 12y ago
>Typically PHP stuff where the paid developers hyperoptimise for MySQL
That's quite true. My experience with MySQL comes from working with company intranet installations that didn't see that much traffic and some web apps, all with a high read-to-write request ratio. They all ran off a single DB server (some hardware, some VPS), so my administrative work was limited to automating fairly straightforward tasks with things like Ansible. I'm curious to hear an example of the kinds of problems you've run into with MySQL, since I assume you deal with more complex and larger-scale deployments. (And I'm looking for anecdotes to help persuade customers and developers alike to give Postgres a try.)
- davidgerard 12y agoNothing hugely complicated. Production Magento, Drupal and WordPress - we managed to outsource the WordPress, so now it's mainly now Magento, and that's much more horrible in itself than MySQL - one in-house tool that used to use it, some MediaWiki, and one really badly-behaved in-house tool that picked MySQL without asking us first. Mostly we were bitten by long-running MySQL sillinesses: * its strange idea of UTF-8 (we call the MySQL version WTF-8 - see http://geoff.greer.fm/2012/08/12/character-encoding-bugs-are-%F0%9D%92%9Cwesome/ http://geoff.greer.fm/2012/08/12/character-encoding-bugs-are... ) * InnoDB's galloping disk consumption * the Debian/Ubuntu package's default stupid behaviour of putting all the InnoDB databases into a single file ibdata1 (I hope this is a Debianism and not something that's default in upstream) * ibdata1 never shrinking ever (bug #1341, open since 2003) * binary replication issues (e.g. bug #68892, which is fixed but that doesn't help older or distro versions) * several others I've mercifully obliterated the braincells that were holding them. But all of these were long-known issues that will never be fixed for one reason or another (backward compatibility with past mistakes, or they just can't be bothered). Here's a good crib: http://grimoire.ca/mysql/choose-something-else http://grimoire.ca/mysql/choose-something-else tl;dr MySQL: the Comic Sans of databases. Except Comic Sans has use cases.
- proveanegative 12y agoThanks for the list. I'll bookmark it just in case.
- davidgerard 12y agoI also made this a blog post: http://reddragdiva.dreamwidth.org/593924.html http://reddragdiva.dreamwidth.org/593924.html Some hopefully useful comments there, and on G+: https://plus.google.com/u/0/111502940353406919728/posts/gHwpULoqraK https://plus.google.com/u/0/111502940353406919728/posts/gHwp...