| Bug #81442 | Unable to analyze table whilst super_read_only is enabled | ||
|---|---|---|---|
| Submitted: | 16 May 2016 22:12 | Modified: | 24 Jan 2018 16:08 |
| Reporter: | Ceri Williams | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Options | Severity: | S3 (Non-critical) |
| Version: | 5.7.12,5.7.15,8.0.0,8.0.4-rc | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | analyze, super_read_only | ||
[17 May 2016 9:05]
MySQL Verification Team
Hello Ceri Williams, Thank you for the report. Thanks, Umesh
[1 Feb 2017 23:18]
Ceri Williams
Related "super_read_only and read_only not allowing OPTIMIZE TABLE on 5.7" https://bugs.mysql.com/bug.php?id=84081
[24 Jan 2018 16:08]
Ceri Williams
Still present on 8.0.4-rc
Description: It is not possible to perform an ANALYZE TABLE directly on a server running in super_read_only mode. How to repeat: mysql [localhost] {msandbox} ((none)) > set global super_read_only = 0; Query OK, 0 rows affected (0.00 sec) mysql [localhost] {msandbox} ((none)) > create table test.a (id integer); Query OK, 0 rows affected (0.08 sec) mysql [localhost] {msandbox} ((none)) > set global super_read_only = 1; Query OK, 0 rows affected (0.00 sec) mysql [localhost] {msandbox} ((none)) > analyze table test.a; ERROR 1290 (HY000): The MySQL server is running with the --super-read-only option so it cannot execute this statement Suggested fix: Enable the ANALYZE whilst running in super_read_only mode to allow for key distribution of tables to be updated outside of replication