Here’s the background: I’m testing many features of MySQL 5.6.7-RC due to two reasons:
- I’m verifying my common_schema installs and works properly on 5.6
- I promised I would present a 45 minute “what’s new in MySQL 5.6” seminar in the upcoming OracleWeek (Israel)
In the case of common_schema, I have managed to find one weird bug (a behavior regression from 5.5) and one server-crashing bug, by merely running the project’s tests, known to pass on 5.1 and 5.5 (and not utilizing any 5.6 features).
In the case of my presentation, I’m getting acquainted with new syntax and functionality, and am getting unexpected results. I’ve hit replication issues and locking issues in online DDL.
If I am able to find these bugs within a few hours of experimenting & testing, then it is safe to assume we can extrapolate to many more bugs. This is not surprising; 5.6 boasts some 120 new features (I didn’t actually count them). Of course they would introduce new bugs.
The moral is this: if you’re interested in 5.6 as I am – and there’s a lot to wait for – please consider experimenting with it, and report as many bugs to bugs.mysql.com as possible. Reporting bugs is the user’s authoritative way of improving an open source product and pushing towards a stable release. Provide your feedback today!
Thanks for testing and reporting! We’re interested in everything from outright bugs to things that don’t seem to work as well together as they could. Please keep up the good work!
We’ve reproduced the crashing one and it’ll probably be fixed in the next build.
Views are my own, for an official view, seek a PR person.
James Day, MySQL Senior Principal Support Engineer, Oracle
If possible, please post the details of the crash bug.
The bug isn’t visible on the bug tracker..
Is this fixed in 5.6 http://www.xaprb.com/blog/2012/08/28/debugging-metadata-locking-in-mysql-5-5/
I wouldn’t even know how to write up that bug report
@M
Don’t know