I've got a question from colleague last night on what bugs should
users take into account if they plan to upgrade to MySQL 5.6 now.
Simple answer is: it depends. If one of the new features or
scalability improvements are really important, then bugs in other
features or clearly identified problematic use cases may be just
ignored or avoided.
But to be on a safe side users should at least check if they are (or may be) affected by a known regression bugs, when new version is slower or produce wrong results or crashes in cases that worked without problems before.
List of bugs in MySQL 5.6 that can be formally …