mirror of
https://github.com/MariaDB/server.git
synced 2025-01-30 18:41:56 +01:00
727491b72a
This includes all test changes from
"Changing all cost calculation to be given in milliseconds"
and forwards.
Some of the things that caused changes in the result files:
- As part of fixing tests, I added 'echo' to some comments to be able to
easier find out where things where wrong.
- MATERIALIZED has now a higher cost compared to X than before. Because
of this some MATERIALIZED types have changed to DEPENDEND SUBQUERY.
- Some test cases that required MATERIALIZED to repeat a bug was
changed by adding more rows to force MATERIALIZED to happen.
- 'Filtered' in SHOW EXPLAIN has in many case changed from 100.00 to
something smaller. This is because now filtered also takes into
account the smallest possible ref access and filters, even if they
where not used. Another reason for 'Filtered' being smaller is that
we now also take into account implicit filtering done for subqueries
using FIRSTMATCH.
(main.subselect_no_exists_to_in)
This is caluculated in best_access_path() and stored in records_out.
- Table orders has changed because more accurate costs.
- 'index' and 'ALL' for small tables has changed to use 'range' or
'ref' because of optimizer_scan_setup_cost.
- index can be changed to 'range' as 'range' optimizer assumes we don't
have to read the blocks from disk that range optimizer has already read.
This can be confusing in the case where there is no obvious where clause
but instead there is a hidden 'key_column > NULL' added by the optimizer.
(main.subselect_no_exists_to_in)
- Scan on primary clustered key does not report 'Using Index' anymore
(It's a table scan, not an index scan).
- For derived tables, the number of rows is now 100 instead of 2,
which can be seen in EXPLAIN.
- More tests have "Using index for group by" as the cost of this
optimization is now more correct (lower).
- A primary key could be preferred for a normal key, even if it would
access more rows, as it's faster to do 1 lokoup and 3 'index_next' on a
clustered primary key than one lookup trough a secondary.
(main.stat_tables_innodb)
Notes:
- There was a 4.7% more calls to best_extension_by_limited_search() in
the main.greedy_optimizer test. However examining the test results
it looked that the plans where slightly better (eq_ref where more
chained together) so I assume this is ok.
- I have verified a few test cases where there was notable/unexpected
changes in the plan and in all cases the new optimizer plans where
faster. (main.greedy_optimizer and some others)
97 lines
3 KiB
PHP
97 lines
3 KiB
PHP
eval create table t1 (a timestamp not null DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, primary key(a)) engine=$engine
|
|
partition by key (a) (
|
|
partition pa1 max_rows=20 min_rows=2,
|
|
partition pa2 max_rows=30 min_rows=3,
|
|
partition pa3 max_rows=30 min_rows=4,
|
|
partition pa4 max_rows=40 min_rows=2);
|
|
show create table t1;
|
|
insert into t1 values ('1975-01-01 21:21:21'), ('2020-12-31 12:10:30'), ('1980-10-14 03:03'), ('2000-06-15 23:59');
|
|
--sorted_result
|
|
select * from t1;
|
|
select * from t1 where a=19801014030300;
|
|
delete from t1 where a=19801014030300;
|
|
--sorted_result
|
|
select * from t1;
|
|
drop table t1;
|
|
|
|
eval create table t2 (a timestamp not null DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, primary key(a)) engine=$engine
|
|
partition by key (a) partitions 12;
|
|
show create table t2;
|
|
insert into t2 values ('1975-01-01 0:1:1'), ('2020-12-31 10:11:12'), ('1980-10-14 13:14:15'), ('2000-06-15 14:15:16');
|
|
--sorted_result
|
|
select * from t2;
|
|
select * from t2 where a='1980-10-14 13:14:15';
|
|
delete from t2 where a='1980-10-14 13:14:15';
|
|
--sorted_result
|
|
select * from t2;
|
|
delete from t2;
|
|
let $count=59;
|
|
--echo $count inserts;
|
|
--disable_query_log
|
|
begin;
|
|
while ($count)
|
|
{
|
|
eval insert into t2 values (19710101000000+$count);
|
|
dec $count;
|
|
}
|
|
commit;
|
|
--enable_query_log
|
|
select count(*) from t2;
|
|
--sorted_result
|
|
select * from t2;
|
|
drop table t2;
|
|
|
|
################################################################################
|
|
# The following 2 tests are no longer valid after bug #42849 has been fixed:
|
|
# it is not possible to use a timezone-dependent (such as month(timestamp_col)
|
|
# or just a timestamp_col in a numeric context) anymore.
|
|
################################################################################
|
|
|
|
# eval create table t3 (a timestamp not null, primary key(a)) engine=$engine
|
|
# partition by range (month(a)) subpartition by key (a)
|
|
# subpartitions 3 (
|
|
# partition quarter1 values less than (4),
|
|
# partition quarter2 values less than (7),
|
|
# partition quarter3 values less than (10),
|
|
# partition quarter4 values less than (13)
|
|
# );
|
|
# show create table t3;
|
|
# let $count=12;
|
|
# --echo $count inserts;
|
|
# --disable_query_log
|
|
# SET TIME_ZONE= '+03:00';
|
|
# begin;
|
|
# while ($count)
|
|
# {
|
|
# eval insert into t3 values (date_add('1970-01-01 00:00:00',interval $count-1 month));
|
|
# dec $count;
|
|
# }
|
|
# commit;
|
|
# --enable_query_log
|
|
# select count(*) from t3;
|
|
# select * from t3;
|
|
# drop table t3;
|
|
|
|
# eval create table t4 (a timestamp not null, primary key(a)) engine=$engine
|
|
# partition by list (month(a)) subpartition by key (a)
|
|
# subpartitions 3 (
|
|
# partition quarter1 values in (0,1,2,3),
|
|
# partition quarter2 values in (4,5,6),
|
|
# partition quarter3 values in (7,8,9),
|
|
# partition quarter4 values in (10,11,12)
|
|
# );
|
|
# show create table t4;
|
|
# let $count=12;
|
|
# --echo $count inserts;
|
|
# --disable_query_log
|
|
# begin;
|
|
# while ($count)
|
|
# {
|
|
# eval insert into t4 values (date_add('1970-01-01 00:00:00',interval $count-1 month));
|
|
# dec $count;
|
|
# }
|
|
# commit;
|
|
# --enable_query_log
|
|
# select count(*) from t4;
|
|
# select * from t4;
|
|
# drop table t4;
|