MySQL Doesn’t Always Suck; This Time it’s AMD

I would say MySQL's response sucked plenty. No effort was made to document the issue for end-users in the release notes. No effort was made to document a workaround that end-users could implement. No attempt was made to provide a workaround in the code; if a workaround was truly impossible as claimed, then why not implement a killswitch to prevnt MySQL from running in such a configuration?

Quick reference: cat /proc/cpuinfo<p>Your processor is buggy if it's an Opteron family 15, models 32-63 inclusive.