This week we had finally got MySQL 5.6.10 released as GA. It's a big deal, first MySQL GA release with the entire development process happened in Oracle from day one, quantum leap (as every second blog post says these days) in many areas, from scalability to replication performance, with InnoDB fulltext indexes and PERFORMANCE_SCHEMA improvements in between... So, this week it makes sense to concentrate on 5.6 GA and nothing else.
As one of my former colleagues noted, no GA is bug free. Surely there are known and verified bugs in 5.6.10, but not that many. Let me just give you a list to check, in case you plan to upgrade/switch to 5.6 in production:
- Bug #68300 (crash when password expire is set for a user, in a corner case)
- Bug #68299 (EXPLAIN output for UPDATE/DELETE can still be wrong)
- Bug #68277 (problem to build with system zlib)
- Bug #68251 (semisync replication)
- Bug #68250 (semisync replication)
- Bug #68220 (minor, when replication info is stored in tables)
- Bug #68192 (data types)
- Bug #68171 (missing manual)
- Bug #68165 (upgrade)
- Bug #68164 (minor, replication from older versions)
- Bug #68163 (minor, upgrade)
- Bug #68144 (custom charsets, regression)
- Bug #68118 (installing)
- Bug #68107 (client crash, ujis charset)
- Bug #68097 (incomplete manual)
- Bug #68079 (scalability for joins)
- Bug #68041 (zero date, regression)
- Bug #68040 (zero date, InnoDB)
- Bug #68019 (table lost during ALTER)
- Bug #67982 (partitioning)
These were mostly new bug reports, since December 27, 2012. Some older reports may also still be valid, but not many. I've carefully checked the last list of bugs "that would be nice to fix
in MySQL 5.6 before GA" that I'd created while still working in Oracle,
dated August 26, 2012. Of the bugs listed there only Bug #64683 is still "Verified" (I had not checked if it is repeatable). The rest were closed mostly at RC stage or even before 5.6.8.
I keep monitoring number of open bug reports that require processing, and this week it was around 320, below the level of August, 2012, even though inflow increased a bit since 5.6 GA announcement, as community users started to check 5.6 more actively.
Does this mean that Oracle does a good job and we should not care much about bugs processing now? Not 100% sure yet.
Some bug reports about the new features started to appear soon after GA announcement and still need Oracle attention. Check Bug #68281, for example, before relying on multi-threaded slave as a solution to all your replication performance problems. Users claim they get wrong results from 5.6.10, see Bug #68001, but nobody cares to reply. Business as usual :)
Anyway, I plan to check how bugs processing works without external influence via Facebook. That's why I stop regular posting about MySQL server bugs until official 5.6.11 release. Let's see what happen if I leave Oracle alone for some time.