With the upcoming release of MySQL 5.7 I begin to see a problem which I think needs attention at least for 5.8 or whatever comes next. The GA release cycle is too long, being about 2 years and that means 3 years between upgrades in a production environment More people use MySQL and the data … Continue reading Making MySQL Better More Quickly
MySQL Bugs On Dolphins, Panda's and Bugs
Like any good OpenSource project the MySQL Bugs website is open for anyone to search through. This ofcourse doesn't include the security bugs.
There is a second collection of bugs in the My Oracle Support and these bugs are only accesseble by customers with a support contract. Even when I have access to MOS I still prefer to use the community bugs site. For service requests etc. I would use MOS.
The openness of the bugs database is one of the topic the IOUG MySQL Council discusses with Oracle.
The bugs database has more to offer than just information about initial bugs:
- Bugs Statistics: This has a big matrix with …
Using MySQL Sandbox I can install multiple instances of MySQL. It is not uncommon for me to run 5 or 6 instances at once, and in some occasions, I get to have even 10 of them. It is usually not a problem. But today I had an issue while testing MariaDB, for which I needed 5 instances, and I the installation failed after the 4th one. To make sure that the host could run that many servers, I tried installing 10 instances of MySQL 5.6 and 5.7. All at once, for a grand total of 20 instances:
$ make_multiple_sandbox --how_many_nodes=10 5.6.14
installing node 1
installing node 2
installing node 3
installing node 4
installing node 5
installing node 6
installing node 7
installing node 8
installing node 9
installing node 10
group directory installed in $HOME/sandboxes/multi_msb_5_6_14
$ make_multiple_sandbox --how_many_nodes=10 5.7.4 …
It seems Oracle released MySQL 5.6.19 yesterday. So, it's time to check
what community bug reports are fixed there.
Let's start with InnoDB. We have the following bugs fixed:
- Bug #72079, "Upgrade from 5.6.10 to 5.6.16 crashes and leaves unusable DB". Honestly I had not noted this bug, even though I upgrade several instances on Windows to each and every release since 5.6.8. Probably because I had no need to use FTS indexes till recently...
- Bug #71014, about two extra memset calls that are now removed. I hope the patch bug report provided was just used.
Oracle engineers suppose to open new bugs in its internal bug
database until they think opening them in public one makes
Example of such a case is Bug #68415 "resolveip and mysqlaccess still use gethostbyaddr"
Reason for making it public is that it describes behavior, which was introduced into the tools resolveip and mysqlaccess without intention and they now still can work with NetBIOS name, different or not existent in DNS while MySQL server cannot.
Interesting fact that such NetBIOS names were not ever officially supported, but they worked until deprecated function gethostbyaddr was replaced with recommended to use …[Read more]
I think that MySQL Manual is one of the reasons why MySQL became
and still remains popular. I find a lot of useful information (at
least references to share with customers, if not real insights)
there even after 9+ years of working with MySQL every day and
with all numerous articles and blog posts on most important
topics available now. I still have MySQL manual page open at
every browser instance on every laptop I use on a regular
It's simply great, well indexed by Google and has meaningful human-readable URLs, so one can even guess them for the topics he need. I have http://dev.mysql.com/doc/refman/5.6/en/merge-storage-engine.html open right now and looking at it I clearly understand without any search that if I need a reference for SELECT syntax in 5.5 I have just replace "5.6" with "5.5" and "merge-storage-engine" with …
Over the past few years, we’ve seen MySQL technology advance in leaps and bounds, especially when it comes to scalability. But by focusing on the internals of the storage engine for so long, MySQL has fallen behind regarding support for advanced SQL features.
Why is this significant? It means that MySQL is now the only widely-used SQL implementation that does not support recursive queries. Fifteen years after it was defined in the SQL standard, almost every other SQL database of note has supported this feature:
As you should already know, Oracle had released MySQL 5.6.16
officially on January 31, 2014. You can find all the details in
official release notes. In this post I decided
to concentrate on important fixes for bugs reported by community
in 4 most important categories: InnoDB, replication, partitioning
Let's start with Bug #70768, "Persistent optimizer statistics often causes LOCK_open stalls". It's well known that persistent statistics for InnoDB tables stored in two (again, InnoDB) tables in mysql database may cause various problems, not only bad plans based on outdated statistics there. One of these problems seems solved in 5.6.16, but note that the bug report itself is closed without any specific comment on what exactly was fixed.
Surely, I am not the only one in Percona who reports MySQL bugs.
In my old post, "17 Famous MySQL Bug Reporters", I've already
mentioned Roel Van de Paar, Alexey Kopytov and Peter Zaitsev.They had contributed a lot over
In this post I'd like to concentrate on bug reports from my Support colleagues at Percona. Many of their contributions are …
In the previous post in this series I've listed 15 MySQL bug
reports, documentation and feature requests I've made in 2013
that got fixes or any other kind of solution. Now it's time to
check what happened to the rest and try to think why.
First of all, no MySQL bug reporter is perfect (if only Domas), so some bug reports may be false alarms ("Not a bug"), to hard to fix at any foreseeable future ("To be fixed later") or asking for something that Oracle does not plan to provide …