ANALYZE TABLE crashes debug build on --innodb-read-only instance
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
High
|
Laurynas Biveinis | |||
5.7 |
Fix Released
|
High
|
Laurynas Biveinis |
Bug Description
--source include/
CREATE TABLE t1 (a INT PRIMARY KEY) ENGINE=InnoDB;
INSERT INTO t1 VALUES (1);
--source include/
ANALYZE TABLE t1;
--source include/
DROP TABLE t1;
results in
2016-12-01 11:15:32 7000030b6000 InnoDB: Assertion failure in thread 123145353388032 in file dict0stats_bg.cc line 159
InnoDB: Failing assertion: !srv_read_only_mode
...
0 mysqld-debug 0x000000010121e34e my_print_stacktrace + 222
1 mysqld-debug 0x0000000100c86036 handle_fatal_signal + 1558
2 libsystem_
3 ??? 0x0000000000000006 0x0 + 6
4 libsystem_c.dylib 0x00007fff9baf0420 abort + 129
5 mysqld-debug 0x000000010136ebb1 _Z26dict_
6 mysqld-debug 0x000000010140b0aa _ZN11ha_
7 mysqld-debug 0x000000010140cd1d _ZN11ha_
8 mysqld-debug 0x0000000100cf9ffd _ZL17mysql_
9 mysqld-debug 0x0000000100cfb5cc _ZN21Sql_
10 mysqld-debug 0x0000000100e4d1f7 _Z21mysql_
11 mysqld-debug 0x0000000100e48f48 _Z11mysql_
12 mysqld-debug 0x0000000100e430da _Z16dispatch_
13 mysqld-debug 0x0000000100e4771d _Z10do_commandP3THD + 1117
14 mysqld-debug 0x0000000100d83f2a _Z24do_
15 mysqld-debug 0x0000000100d83a9d handle_
16 mysqld-debug 0x000000010173eb6e pfs_spawn_thread + 462
17 libsystem_
18 libsystem_
19 libsystem_
This is a regression introduced by bug 1626441 fix.
https:/ /github. com/percona/ percona- server/ pull/1221 /github. com/percona/ percona- server/ pull/1222
https:/