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]
10 Older Entries »
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:
- Bug #94431 - "Can't upgrade from 5.7 to 8.0 if any database have a hyphen in their name". It seems one actually needs a database like that created in MySQL 5.6 with at least one InnoDB table having FULLTEXT index to hit the problem. Great finding by Phil Murray. Note that after several unsuccessful attempts by others the bug was eventually reproduced and verified by …
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
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:
- 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 …
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
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
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 …
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 …
Oracle had formally released MySQL 5.7.21 yesterday. I do not
bother any more to study MySQL release notes carefully and
completely, but during a quick review today I've noted several
interesting items I'd like you to pay attention to.
I am historically interested in InnoDB implementation details, so I could not miss Bug #87619 - "InnoDB partition table will lock into the near record as a condition in the use ". This was a regression bug in 5.7+, probably caused by new implementation of partitioning in InnoDB.
Another interesting bug is Bug #86927 - "Renaming a partitioned table does not update mysql.innodb_table_stats.", by …
10 Older Entries »