My previous post from this series was published
more than 1.5 years ago. I had never planned to stop writing
about my everyday work on a regular basis, but sometimes it's not
easy to pick up something really interesting for wider MySQL
audience and when in doubts I always prefer to write about MySQL
bugs...
In any case, any long way starts from the first step, so I
decided to write one post in this series per week and try to
summarize in it whatever findings, questions, discussions, bugs
and links I've collected over the week. My work experience
differs week after week, so some of these posts may be boring or
less useful, but I still want to try to create them on a regular
basis.
I was working on (upcoming) blog post (inspired by one customer
issue) on …
We have a public holiday here today and it's raining outside for
a third day in a row already, so I hardly have anything better to
do than writing yet another review of public MySQL bug reports
that I've subscribed to recently.
Not sure if these reviews are really considered useful by anyone
but few of my readers, but I am still going to try in a hope to
end up with some useful conclusions. Last time I've stopped on Bug
#94903, so let me continue with the next bug in my
list:
- Bug #94912 - "O_DIRECT_NO_FSYNC possible …
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]
I've got few comments to my post on references to MariaDB in MySQL bug
reports (not in the blog, but via social media and in personal messages), and all
but one comments from current and former colleagues whose opinion
I value a lot confirmed that this really looks like a kind of
attempt to advertise MariaDB. So, from now on I'll try to keep my
findings on how tests shared by MySQL bug reporters work in
MariaDB for myself, MariaDB JIRA and this blog (where I can and will
advertise whatever makes sense to me), and avoid adding them to
MySQL bug reports.
That said, I still think that it's normal to share links to
MariaDB bug reports that add something useful (like patches, …
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 …
In the just-released MySQL 8.0.14 I added a feature called LATERAL derived tables.
The manual describes the syntax and has examples of how the feature can be used to find greatest values in tables. In the present post I’m going to consider a different problem solved by LATERAL: let’s say that we have a bunch of nodes, and want to make a “random graph”, by connecting every node to other nodes.…
Facebook Twitter Google+ LinkedIn
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: