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 …
Today I'd like to continue my review of public MySQL bug reports with a
list of some bugs I've subscribed to over last 3 weeks. It's
already long enough and includes nice cases to check and share.
Note that I usually subscribe to a bug either because it directly
affects me or customers I work with, or I consider it technically
interesting (so I mostly care about InnoDB, replication,
partitioning and optimizer bugs), or it's a "metabug" - a problem in the way public bug report
is handled by Oracle engineers. These are my interests related to
MySQL bugs.
As usual, I start with the oldest bugs and try to mention bug
reporters by name with links to their other reports whenever this
may give something useful to a reader. I try …
More than 3 weeks passed since my previous review of public MySQL bug reports I
am subscribed to, so it's time to present some of the bugs I've
considered interesting in January, 2019.
As usual, I'll review them starting from the oldest and try to
summarize my feelings about these bugs at the end of this post.
Here they are:
- Bug #93806 - "Document error about ON DUPLICATE KEY UPDATE". Years pass, but fine MySQL manual still does not explain some cases of InnoDB locking properly. Xiaobin Lin found yet another case that it does not explain properly. Or, maybe, the manual is correct and the problem in …
This year I had not only spoken about MySQL bugs reporting at FOSDEM, but spent almost
the entire day listening at MySQL, MariaDB and Friends Devroom. I missed
only one talk, on ProxySQL, (to get some water, drink a
bottle of famous Belgian beer and chat with my former colleague
in MySQL support team, Geert, whom I had not seen for a decade). So,
for the first time out of my 4 FOSDEM visits I've got a first
hand impression about the entire set of talks in the devroom that
I want to share today, while I still remember my feelings.
Most of the talks have both slides and videos …
Today I'd like to continue my tradition of ignoring MySQL 8 (after all,
I can not even build 8.0.14 any more on my Ubuntu
14.04, it's not supported suddenly because of old gcc
version) and, of all MySQL server versions released by Oracle
this week, concentrate on bugs reported in public bugs database
and fixed in the latest minor release of MySQL 5.7 branch,
5.7.25.
This time there is only one InnoDB community-reported bug
fixed, Buig #87423 - "os0file.cc assertion failed
'offset > 0' in os_file_io_complete", from Vasily
Nemkov. See also it's duplicate, …
Slides for my talk about MySQL bugs at FOSDEM 2019 MySQL, MariaDB and Friends Devroon are ready,
support customers decided not to break anything badly on weekend,
so I have some free time for blogging. As usual, when I do
not have any better idea or useful recent real life experience to
share I write about MySQL bugs.
Today I'd like to continue my review of interesting MySQL bug reports
added by Community members in December, 2018. I'll review them
starting from the oldest:
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:
These days several kinds and forks of MySQL are widely used, and
while I promised not to write about MySQL bugs till
the end of 2018, I think it makes sense to try to explain basic
details about bug reporting for at least one of vendors that use
JIRA instances as a public bug tracking systems. I work for
MariaDB Corporation and it would be natural for me to write about
MariaDB's JIRA that I use every day.
As a side note, Percona also switched to JIRA some time ago, and many of the JIRA-specific
details described below (that are different comparing to good old
https://bugs.mysql.com/) apply to Percona bugs …
From the lack of comments to my previous post it seems everything is clear with ERROR 1213 in different kinds and forks of MySQL. I may still write a post of two about MyRocks or TokuDB deadlocks one day, but let's get back to my main topic of MySQL bugs. Today I continue my series of posts about community bug reports I am subscribed to with a review of bugs reported in November, 2018, starting from the oldest and skipping those MySQL 8 regression ones I've already commented on. I also skip documentation bugs that should be a topic for a separate post one day (to give more illustration to …
[Read more]