Fun with Bugs #77 - On MySQL Bug Reports I am Subscribed to, Part XIV

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 continuemy review of interesting MySQL bug reports added by Community members in December, 2018. I'll review them starting from the oldest:

• Bug #93701  - " Assertion `maybe_null' failed |Item_func_concat::val_str(String*) ". It's debug assertion, not a big deal (S6 bug), so why should anyone care about this report from Ramesh Sivaraman ? Because last time same assertion failure ended up as serious enough Bug #83115 fixed in 8.0.11.
• Bug #93708  - " Page Cleaner will sleep for long time if clock changes ". In this bug report from Marcelo Altmann I was mostly impressed by arguing started by Oracle engineer on bug severity (documentation request, feature request vs real bug). IMHO it was a waste of time.
• Bug #93728  - " mysqld crash after using alter table with SPATIAL key ". Nice finding by Rui Xu . Unfortunately MariaDB 10.3.7 is also affected. At least in the error log I also see this error message for each SPATIAL index of the table:
  

  2019-01-20 19:26:15 9 [ERROR] InnoDB: Record in index `idx2` of table `test`.`tab` was not found on update: TUPLE (info_bits=0, 2 fields): {[32]      $@      $@

  $@      $@(0x0000000000000400000000000000040000000000000004000000000000000

  400),[4]    (0x00000001)} at: COMPACT RECORD(info_bits=0, 1 fields): {[8]infimum

  (0x090E06090D050D00)}

• Bug #93734  - " MySQL 8.0 is 36 times slower than MySQL 5.7 ". I like everything about this bug reported by Vadim Tkachenko , CTO of Percona. I like synopsis that sounds cool, missing exact MySQL 8.0.x version (but I suspect 8.0.13), impact of innodb_flush_log_at_trx_commit , suggested fix and the fact that the bug is still "Open" and nobody from Oracle paid any attention to the report from CTO of one of key Oracle partners and supporters of MySQL 8. Wonderful!
• Bug #93737  - " mysqlbinlog mermory used grows unstoped ". I had not tried to reproduce it (and nobody had it seems, as the bug is still "Open"), but this report by Chandler Bong sounded interesting. Let's see what it may end up with...
• Bug #93746  - " MySQL Crashes with deadlock at Mutex DICT_SYS created dict0dict.cc:1172 ". Long semaphore waits involving DICT_SYS mutex and leading to watchdog thread killing MySQL are common. Bug processing is still in progress, but I subscribed to this bug by Anton Ravich mostly to follow another bug he refers to as a possibly related, Bug #80919 . That bug is declared a duplicate of some bug in Oracle's internal bugs database, without bug number mentioned. This is not the first time I see such am artistic way to process community bugs (that I consider totally wrong and unacceptable).
• Bug #93760  - " InnoDB got assert failure while figuring out space id at startup ". Fungo Wang found this crash while running MTR test case innodb.innodb_redo_debug_1 with debug binaries. Now I wonder if Oracle QA runs MTR tests with debug binaries at all and do they care to check failures (or rely on Percona for this activity)? Any comments?
• Bug #93761  - " optimize table cause the slave MTS deadlock! ". Sounds interesting and serious, but nobody cared to check this bug report. It's "Open" without comments for 3 weeks already.
• Bug #93767  - " INSTALL COMPONENT fails - handled segfault during installation nothing in log ". I am surprised that somebody outside of Oracle already uses new MySQL 8.0 server components feature. My former colleague, Justin Swanhart , tried but failed so far. Let's see how this report may end up. For now Oracle engineer stated that Justin tried to do something this framework was not designed for, see nice last comment there.
• Bug #93777  - " the Originator of mysql.event is not correct ". Pay attention to this bug found by Dennis Gao if you use events in replication environment.
• Bug #93779  - " dml in table with trigger to other Table map in binlog lead to slave sql stopped ". Work on this bug report from Mohamed Atef is still in progress. Bug reported cared to add a lot of details in recent comments, so I hope to see this bug processed soon.

I've also included a couple of bugs reported in January, 2019 in the list above, but I hope you don't mind.

Today I'd like to remember those sunny days in Venice in September and those pesky MySQL bugs reported this winter...

To summarize:

1. Some bug reports stay "Open" for weeks without any good reason recently.
2. The shameful practice of referring to bugs in Oracle's internal bugs database without giving a number (that we see in release notes when the bug is fixed and can look for in commit messages at GitHub) should be stopped! Next time I'll blame engineer(s) who this by name, here and in social media. Check how this is properly done by Shane Bester .
3. I wonder if Oracle QA runs MTR tests cases on debug builds on a regula basis and checks the results, or this is now a job for Percona mostly?
4. I should write a separate blog post about bugs related to SPATIAL indexes implementation in InnoDB. There should be dragons...

P.S. Don't forget to click on names of bug reporters to see the entire list of still active MySQL bug reports each of them created.