Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.6, 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.3(EOL)
-
None
Description
--source include/have_partition.inc
|
--source include/have_innodb.inc
|
|
SET @tx= @@global.tx_read_only; |
|
CREATE TABLE t (a INT) ENGINE=InnoDB PARTITION BY RANGE (a) (PARTITION p VALUES LESS THAN MAXVALUE); |
SET GLOBAL tx_read_only = ON; |
--connect (con1,localhost,root,,)
|
ANALYZE TABLE t; |
|
# Cleanup
|
--disconnect con1
|
connection default; |
DROP TABLE t; |
SET GLOBAL tx_read_only = @tx; |
10.6 686865e112fa4840376745194349845f8d00a2a7 |
ANALYZE TABLE t;
|
Table Op Msg_type Msg_text
|
test.t analyze error Partition p returned error
|
test.t analyze status Engine-independent statistics collected
|
test.t analyze status Operation failed
|
(Engine-independed statistics is irrelevant here, it's just collected in MTR by default. The partition error happens without it as well).
Not reproducible on 10.5.