While MySQL 8.0.x hardly has much impact on my regular work,
recent MySQL 5.7.20 release is something to check carefully.
MySQL 5.7 is widely used in production, as a base for Percona
Server 5.7, some features may be merged into MariaDB 10.x etc.
So, here is my review of some community reported bugs that were
fixed in recently released MySQL 5.7.20, based on the release notes.

Usually I start with InnoDB bug fixes, but in 5.7.20 several
related fixes were made only to bugs reported internally. So,
this time I have to start with partitioning:

MySQL 5.6.27 was released on September 30
formally. Source code is also available on GitHub, and I have it compiled (some users are
less lucky) and running for a couple of days
already. In this post I'll comment on some bugs reported by MySQL
Community that are fixed there.

I'd like to start with a couple of bugs where patches were also
contributed. First of all, the fix suggested by Stewart
Smith in Bug
#72811, "Set NUMA mempolicy for optimum mysqld performance",
helps to allocate memory in a more reasonable way on NUMA-enabled
systems. Previously it was like all interleaved or nothing, now
there is a way to apply this only …

A few days ago I reported on a problem with savepoints, but all
that it appeared to be was an extemporaneous warning message.
Well, I just found out that InnoDB can actually lose the
savepoints! The overall transaction can still be rolled back
successfully, but the savepoints themselves are completely gone.
This only occurs after the warning: "Got error 153 from storage
engine" happens twice in one transaction (if it only happens
once, the savepoints still work) which requires that alternating
savepoints be set 6 times. See the full report here: http://bugs.mysql.com/bug.php?id=38187.

One of our developers ran into the strangest error a few days
ago, which neither the MySQL manual nor Google searching could
find any information on. When he called certain stored procedures
in a certain order, he got "Error 153 returned from storage
engine." It's been reduced to a very simple test case, and a
bug report has been filed. Here's the test
case:

In this article, I'd like to take that to the next level and
demonstrate how to write an information schema plug-in that can
access some of the internals of the MySQL server. For this
particular purpose, we will focus on a plug-in that reports all
the SAVEPOINTs available in the current
session. This …

Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.