database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-07-30 16:24:05 +03:00
Code Activity

MDEV-10683: main.order_by_optimizer_innodb fails in buildbot

Browse Source 
Fix order_by_optimizer_innodb and order_by_innodb tests.

The problem was that the query could be ran before InnoDB was
ready to provide a realistic statistic for #records in the table.

It provided a number that was too low, which caused the optimizer
to decide that range access plan wasn't advantageous and discard it.
This commit is contained in:
Sergei Petrunia
2023-10-05 16:57:52 +03:00
parent e4ce61ac0f
commit 422774b40a
4 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
mysql-test/main/order_by_innodb.result
View File

@ -159,6 +159,12 @@ insert into t2 values
(1,2,'2019-03-05 00:00:00','2019-03-06 00:00:00'),
(2,3,'2019-03-05 00:00:00','2019-03-06 00:00:00'),
(3,3,'2019-03-06 00:00:00','2019-03-05 00:00:00');
analyze table t1,t2 persistent for all;
Table Op Msg_type Msg_text
test.t1 analyze status Engine-independent statistics collected
test.t1 analyze status OK
test.t2 analyze status Engine-independent statistics collected
test.t2 analyze status OK
select
t1.id,t2.id
from
@ -177,6 +183,10 @@ id id
2 1
3 3
create index for_latest_sort on t2 (d1 desc, d2 desc, id desc);
analyze table t2 persistent for all;
Table Op Msg_type Msg_text
test.t2 analyze status Engine-independent statistics collected
test.t2 analyze status OK
select
t1.id,t2.id
from