Bug #87738 | mysql_upgrade failed even after removing query cache settings | ||
---|---|---|---|
Submitted: | 12 Sep 2017 12:57 | Modified: | 13 Oct 2017 9:18 |
Reporter: | Simon Mudd (OCA) | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 8.0.3 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | mysql_upgrade |
[12 Sep 2017 12:57]
Simon Mudd
[13 Sep 2017 9:18]
MySQL Verification Team
Hello Simon, Thank you for the report and feedback. I tried to reproduce the error i.e "mysql_upgrade: [ERROR] 1146: Table 'performance_schema.global_status' doesn't exist" but not seeing the issue when I tried binary in place upgrade from 5.7.19 -> 8.0.3. I didn't setup replication and tried to upgrade slave(5.7.19) instead attempted on a standalone 5.7.19 instance. Is there anything else required to reproduce this issue? Could you please provide 5.7.19 conf file from your environment to see if that helps me trigger the error? Please let us know. Also, query_cache_size issue seems to be valid one as query_cache_size is removed in 8.0.3 and documented - https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_query_cache_si... Thanks, Umesh
[3 Oct 2017 12:11]
Daniƫl van Eeden
I think the query cache settings should be accepted in my.cnf etc. and should then be ignored and/or just cause an deprecation warning.
[14 Oct 2017 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".