After a 3 months long break I'd like to continue
reviewing MySQL bug reports that I am subscribed to. This issue
is devoted to bug reports I've considered interesting to follow
in May, 2019:
Oracle released minor MySQL Server versions in all supported
branches on April 25, 2019. MySQL 5.7.26 is just one of them, but recently I prefer to ignore MySQL 8 releases
(after checking that I can build them from source code at least
somewhere, even if it takes 18G+ of disk space and that they work
in basic tests), as there are more chances for MySQL 5.7 bug
fixes to affect me (and customers I care about) directly.
So, in this yet another boring blog post (that would never be a
reason for any award) I plan to concentrate …
I have not much yet to say on a popular topic of upgrading everything to MySQL 8, so let me just continue reviewing public MySQL bug reports that I've subscribed to recently. After my previous post at least one bug, Bug #94747, got enough comments and clarifications (up to specific commit that introduced this regression pointed out by Daniel Black!) to have it re-classified and verified as InnoDB code bug. So, I see good reasons to continue attracting wide public attention …
[Read more]
Recently I noted that some of my comments to public MySQL bug
reports got hidden by somebody from Oracle with privileges to do
so. I was not able to find out who did that and when, as this
information is not communicated to bug subscribers (this may
change if my feature requests, Bug
#94807 - "Subscriber should be notified when comment is
made private", is eventually implemented).
When it happened for the first time I thought it was probably
non-intentional. When it happened for a second time I complained
with a tweet that got few likes and zero comments.
Recently this happened again and yet another tweet had not got much attention, but
at least I've got a comment via …
Two weeks passed since my previous review of public MySQL bug reports I
consider interesting enough to subscribe to them. Over this
period I picked up a dozen or so new public bug reports that I'd
like to briefly review today.
Here is my recent subscriptions list, starting from the oldest
bug reports:
For some reason the Committee of FOSDEM 2019
MySQL, MariaDB & Friends Devroom of all my talks
submitted picked up the one on how to create a useful MySQL bug
report, so I have no options but continue to write about MySQL
bugs, as long and MySQL Community wants and even prefers to
listen and read about them... That's what I do, with
pleasure.
Today I'll continue my series of posts about community bug reports I am
subscribed to with the review of bugs reported since October 1,
2018, starting from the oldest and skipping those MySQL 8
regression ones I've already commented
on:
More than 2 months passed since my previous review of active MySQL bug reports I
am subscribed to, so it's time to describe what I was interested
in this summer.
Let's start with few bug reports that really surprised me:
Several MySQL releases happened yesterday, but of them all I am
mostly interested in MySQL 5.7.23, as MySQL 5.7 (either directly or
indirectly, via forks and upstream fixes they merge) is probably
the most widely used MySQL GA release at the moment.
In this post (in a typical manner for this "Fun with Bugs"
series) I'd like to describe several bugs reported by MySQL
Community users and fixed in MySQL 5.7.23. As usual, I'll try to
concentrate mostly on InnoDB, replication, partitioning and
optimizer-related bugs (if any).
| … |
In one of my previous posts I stated that in
Oracle's MySQL server some old enough features remain
half-backed, not well tested, not properly integrated with each
other, and not documented properly. It's time to prove
this statement.
I should highlight from the very beginning that most of the
features I am going to list are not that much improved by other
vendors. But they at least have an option of providing other,
fully supported storage engines that may overcome the problems in
these features, while Oracle's trend to get rid of most engines
but InnoDB makes MySQL users more seriously affected by any
problems related to InnoDB.
| … |
Back in April I was preparing for vacations that my wife and I
planned to spend in UK. Among other things planned I wanted to
visit a customer's office in London and discuss few MySQL and MariaDB
related topics, let's call them "stories". I tried to prepare
myself for the discussion and collected a list of known active
bugs (what else could I do as MySQL entomologist) for each of
them. Surely live discussion was not suitable to share lists of
bugs (and for some "stories" they were long), so I promised to
share them later, in my blog. Time to do what I promised had
finally come!
One of the stories we briefly discussed was "partitioning story".
Right now I can immediately identify at least 47 active MySQL
bugs in the related …