Skip to content

# Further experiments with MySQL 5.6.7-RC: submit your bugs

MySQL New Features Opinions October 22, 2012

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!

- Twitter
- LinkedIn
- WhatsApp
- Email
- Facebook
- Print

###
8
Leave a Reply

7 Comment threads
1 Thread replies
0 Followers
Most reacted comment
Hottest comment thread
3 Comment authors
Recent comment authors

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe
Notify of
Guest
James Day

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

Guest
Justin Swanhart

If possible, please post the details of the crash bug.

The bug isn’t visible on the bug tracker..

Guest
M

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

Quora

Is anybody using MySQL 5.6 in production ? If yes, are they using the nosql feature as well?…

MySQL 5.6.7 is RC (release candidate) status, but that may be too optimistic. It appears to have some crash bugs and regressions in behavior and performance. I’m sure subsequent releases will fix these problems, but so far it’s showing itself to be t…

Author
shlomi

@M
Don’t know

Guest
James Day

Quora, yes, there are some pretty major places that are already making some use of 5.6 in production, typically with substantial throughput improvement. It’s part of how we’re getting some excellent feedback about irritations and bugs. We also know of others that are well into testing migration to it. If you’re not trying it yet and have lots of servers, please consider at least running a few replication slaves on it so you can be sure that you’ll quickly find out about any issues that affect you and can file any related bugs. If you only have one production server,… Read more »

Guest
Justin Swanhart

James,

I understand that Oracle doesn’t want black hats to be a problem but seriously, if I want to test my app and there is a crash, I should be able to see if the crash has already been reported by someone else!

Also, what if I want to look for open 5.6 bugs and try to fix them myself? MySQL is supposed to be open source.

Hiding bugs is just wrong, in my opinion. Information should be free.

Guest
James Day

Justin, Say I trust you and write you a check for a prize for finding a bug in a programming book I write. That works well, except… even with such limited distribution, Knuth found that people were abusing the details on the checks to commit fraud on his bank account. If you don’t know the Knuth story, see http://sunburn.stanford.edu/~knuth/news08.html . He could have tried to tell just people he thought he could trust but he already had a pretty high hurdle and that wasn’t working. So he picked an alternative non-discriminatory approach instead. That’s sad but it’s the reality of… Read more »

wpDiscuz
Send to Email Address Your Name Your Email Address Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.