Holidays season is almost over here, so it's time to get back to
my main topic of MySQL bugs. Proper MySQL bug reporting will be a
topic of my FOSDEM 2019 talk in less than 4 weeks (and few
slides with recent examples of bugs are not yet ready), so I have
to concentrate on bugs.
Last time in this series I reviewed some
interesting bug reports filed in November, 2018. Time to move on
and proceed with bugs reported in December, 2018, as I've
subscribed to 27 or so of them. As usual, I'll review them
briefly starting from the oldest and try to check if MariaDB 10.3
is also affected when the bug report is about common
features:
Jan
06
2019
Dec
02
2018
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:
- …
Nov
24
2018
It's time to continue my review of MySQL bug reports that I
considered interesting for some reason recently. I had not got
any notable reaction from Oracle engineers to my previous post about recent regression bugs in
MySQL 8.0.13, so probably this topic is not really that hot. In
this boring post I'll just review some bugs I've subscribed to
since August that are still not closed,
starting from the oldest.
Let me start with a couple of bug reports that remain
"Open":
- Bug #91959 - "UBSAN: signed integer overflow in lock_update_trx_age". It's really unusual to see bug reported by …
Nov
18
2018
I've subscribed to more than 60 new bug reports since my previous post in this series. It means that
I'd need 4-5 posts to cover all new subscriptions and reasons
behind them. I still plan to write about most of the bug reports
I was interested in recently, but for this post I decided to pick
up only MySQL 8.0 regression bugs and pay special attention to
those that could be handled better or faster by Oracle engineers,
as well as those handled perfectly.
The initial reason for this special attention originally
was Bug #93085 - "Stall when concurrently
execute create/alter user with flush privilege", that caused
a lot of interesting Twitter …
Sep
26
2018
A query plan uses loose index scan if “Using index for group-by” appears in the “Extra” column of the EXPLAIN output. In some plans though, “Using index for group-by (scanning)” appears. What does “(scanning)” mean and how is it different from the regular loose index scan?…
Sep
25
2018
Lately, I worked on several queries which started returning wrong results after upgrading MySQL Server to version 5.7 The reason for the failure was derived merge optimization which is one of the default
optimizer_switch
options. Issues were solved, though at the price of performance, when we turned it
OFF
. But, more importantly, we could not predict if any other query would start returning incorrect data, to allow us to fix the application before it was too late. Therefore I tried to find reasons why
derived_merge
can fail. Analyzing the problem
In the first run, we turned SQL Mode
ONLY_FULL_GROUP_BY
on, and this removed most of the problematic queries. That said, few of the queries that were successfully working with
ONLY_FULL_GROUP_BY
were affected.
A quick search in the …
[Read more]
Aug
04
2018
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:
- Bug #91893 - "LOAD DATA INFILE throws error with NOT NULL column defined via SET". The bug was reported yesterday and seem to be about a regression in MySQL 8.0.12 vs older versions. At least I have no problem to use such a way to generate columns for LOAD DATA with MariaDB 10.3.7.
- Bug #91847 - "Assertion `thread_ids.empty()' failed.". As usual, Roel Van de Paar …
May
28
2018
Last time I reviewed my recent subscriptions
to MySQL bugs it was April 1, 2018. I was busy working, blogging
about other bugs, running random MTR tests on MySQL 8.0.11 and
got two weeks of vacation since than. Now it's time to briefly
review 20 recent bug reports (mostly for MySQL 8.0.11) I was
interested in.
As usual, I start with most recent bug reports:
- Bug #91010 - "WolfSSL build broken due to cmake typo". MySQL 8 can be compiled using wolfSSL according to the manual, but as Laurynas Biveinis found this is not the case in practice, and not only because of the typo in libutils.cmake. It seems …
Apr
15
2018
I have some free time today, but I am still lazy enough to work
on numerous planned and pending "ToDo" kind of posts, so why not
to continue review of older MySQL bugs I am
subscribed to. Today I am going to list 15 more bugs reported
more than a year ago and still not fixed:
- Bug #85805 - "Incorrect ER_BAD_NULL_ERROR after LOAD DATA LOCAL INFILE". This detailed bug report by Tsubasa Tanaka stays "Verified" for more than a year already. It's a great example of gdb use for MySQL troubleshooting. Setting a couple of breakpoints may really help to understand how MySQL works and why some …
Apr
01
2018
I've subscribed to more than 15 new MySQL bug reports since
the previous post in this series, so it's time
for a new one. I am trying to follow important, funny or hard to
process bug reports every day. Here is the list of the most
interesting recent ones starting from the latest (with several
still not processed properly):
- Bug #90211 - "Various warnings and errors when compiling MySQL 8 with Clang". Roel Van de Paar and Percona in general continue their QA efforts in a hope to make MySQL 8 better. Current opinion of Oracle …