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:

More than 3 months after 5.7.18 we' ve got MySQL 5.7.19 released
recently. This is my quick review of the release notes with interesting fixed bug
(reported in public) highlighted in the areas I am usually
interested in.

Bug #85043 is still private. You know how much I
hate those. At least we can see it was about the fact that
"The server allocated memory unnecessarily for an operation
that rebuilt the table." Let's hope this is no longer the
case.

is a utility that performs logical backups (which
means backing up your data as SQL statements instead of a raw
copy of data files). It was added in MySQL Server version 5.7.8,
and can be used to dump a database or a set of databases to a
file and then loaded on another SQL server (not necessarily
a MySQL server).

Its usage is similar to

mysqldump

, but it includes a new set of features. Many of the options
are the same, but it was written from scratch to avoid being
limited to

mysqldump

compatibility. The Main Features Include:

To make the dump process faster, it allows parallel
processing of databases and objects within databases. …

Most users of MySQL utilize the mysqldump utility to backup their database. While
mysqldump is handy and easy-to-use (and free), if you have data
which is important to your business, then you should take a look
at the MySQL Enterprise Edition – and use MySQL Enterprise Backup instead. The MySQL Enterprise Backup allows you to backup your
database without the table locking you get with mysqldump. And,
it is extremely fast – especially when you have to restore your
database. Here is a sample speed comparison between MySQL Enterprise Backup and …

We work on data recoveries quite often. In
many cases, we recover table structures from the .frm files
because there was no backup available. There is already a great
blog post by my colleague Miguel Ángel Nieto
about how we can recover structures from .frm files using MySQL
utilities.

This works pretty well and we prefer to run mysqlfrm with the
“–server” option to get all possible information from a .frm
file. However, this option expects that MySQL is up and running
so that mysqlfrm can spawn a new MySQL instance, and run the
structure recovery there.

Recently I came across a tool that makes this job easier.
The name of tool is …

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.