Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.4(EOL), 10.5
Description
http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/14995
10.4 11f3e2366282eb8cf1cb0062793d1020 |
main.partition_innodb 'innodb' w1 [ fail ]
|
Test ended at 2019-07-24 16:28:53
|
|
CURRENT_TEST: main.partition_innodb
|
--- D:/win32-debug/build/src/mysql-test/main/partition_innodb.result 2019-07-24 16:10:28.471773300 +0000
|
+++ D:\win32-debug\build\src\mysql-test\main\partition_innodb.reject 2019-07-24 16:28:53.693111000 +0000
|
@@ -406,7 +406,7 @@
|
insert into t1 values (0), (1), (2), (3);
|
show table status;
|
Name Engine Version Row_format Rows Avg_row_length Data_length Max_data_length Index_length Data_free Auto_increment Create_time Update_time Check_time Collation Checksum Create_options Comment Max_index_length Temporary
|
-t1 InnoDB 10 Dynamic 4 4096 16384 0 0 # NULL # NULL NULL latin1_swedish_ci NULL partitioned 0 N
|
+t1 InnoDB 10 Dynamic 5 3276 16384 0 0 # NULL # NULL NULL latin1_swedish_ci NULL partitioned 0 N
|
drop table t1;
|
create table t1 (a int auto_increment primary key)
|
engine = innodb
|
|
mysqltest: Result content mismatch
|
Attachments
Issue Links
- relates to
-
MDEV-21136 InnoDB's records_in_range estimates can be way off
- Closed
-
MDEV-22119 main.innodb_ext_key fails sporadically
- Closed
-
MDEV-33080 main.innodb_ext_key test case explain estimates 6 rows sometimes
- Open