summaryrefslogtreecommitdiff
path: root/mysql-test/main/range_notembedded.test
blob: 5778cdbd82c406371f08d03f02f63a165cc5ae55 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
#
# Range tests without embedded server. 
#   The first reason to have them is that embedded server doesn't have
#   optimizer trace.
#
--source include/not_embedded.inc
--disable_warnings
drop table if exists t1,t2;
--enable_warnings

--echo #
--echo # MDEV-21958: Query having many NOT-IN clauses running forever
--echo #
create table t2 (
  pk int primary key,
  key1 int,
  col1 int,
  key (key1, pk)
);

insert into t2 (pk, key1) values (1,1),(2,2),(3,3),(4,4),(5,5);

set @tmp_21958=@@optimizer_trace;
set optimizer_trace=1;
explain select * from t2 where key1 in (1,2,3) and pk not in (1,2,3);

--echo # This should show only ranges in form "(1) <= (key1) <= (1)"
--echo #  ranges over "pk" should not be constructed.
select json_detailed(JSON_EXTRACT(trace, '$**.ranges'))
from information_schema.optimizer_trace;
set optimizer_trace=@tmp_21958;

drop table t2;
--echo #
--echo # MDEV-9750: Quick memory exhaustion with 'extended_keys=on'...
--echo #

create table t1 (
   kp1 int,
   kp2 int,
   kp3 int,
   kp4 int,
   key key1(kp1, kp2, kp3,kp4)
);

insert into t1 values (1,1,1,1),(2,2,2,2),(3,3,3,3);
analyze table t1;

show variables like 'optimizer_max_sel_arg_weight';

# 20 * 20 * 20 *20 = 400*400 = 160,000 ranges
set @tmp_9750=@@optimizer_trace;
set optimizer_trace=1;
explain select * from t1 where 
  kp1 in (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20) and
  kp2 in (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20) and
  kp3 in (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20) and
  kp4 in (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20)
;

set @json= (select json_detailed(JSON_EXTRACT(trace, '$**.range_scan_alternatives'))
            from information_schema.optimizer_trace);
--echo # This will show 3-component ranges. 
--echo # The ranges were produced, but the optimizer has cut away kp4
--echo #  to keep the number of ranges at manageable level:
select left(@json, 500);

--echo ## Repeat the above with low max_weight:
set @tmp9750_weight=@@optimizer_max_sel_arg_weight;
set optimizer_max_sel_arg_weight=20;
explain select * from t1 where 
  kp1 in (1,2,3,4,5,6,7,8,9,10) and
  kp2 in (1,2,3,4,5,6,7,8,9,10) and
  kp3 in (1,2,3,4,5,6,7,8,9,10) and
  kp4 in (1,2,3,4,5,6,7,8,9,10)
;
set @trace= (select trace from information_schema.optimizer_trace);
set @json= json_detailed(json_extract(@trace, '$**.range_scan_alternatives'));
select left(@json, 500);

set @json= json_detailed(json_extract(@trace, '$**.setup_range_conditions'));
select left(@json, 2500);

--echo ## Repeat the above with a bit higher max_weight:
set optimizer_max_sel_arg_weight=120;
explain select * from t1 where 
  kp1 in (1,2,3,4,5,6,7,8,9,10) and
  kp2 in (1,2,3,4,5,6,7,8,9,10) and
  kp3 in (1,2,3,4,5,6,7,8,9,10) and
  kp4 in (1,2,3,4,5,6,7,8,9,10)
;
set @json= (select json_detailed(JSON_EXTRACT(trace, '$**.range_scan_alternatives'))
            from information_schema.optimizer_trace);
select left(@json, 1500);

set optimizer_max_sel_arg_weight= @tmp9750_weight;
set optimizer_trace=@tmp_9750;

drop table t1;

--echo #
--echo # MDEV-24739: Assertion `root->weight >= ...' failed in SEL_ARG::tree_delete
--echo #
SELECT *
FROM mysql.help_relation
WHERE NOT (help_topic_id != 8 AND help_keyword_id != 0 OR help_keyword_id = 2 OR help_topic_id < 1900);

SELECT *
FROM mysql.help_relation ignore index (help_topic_id)
WHERE (help_topic_id = 8 OR help_keyword_id = 0) AND help_keyword_id != 2 AND help_topic_id >= 1900;

--echo #
--echo # MDEV-24953: 10.5.9 crashes with large IN() list
--echo #
--source include/have_sequence.inc

CREATE TABLE t1 (
  notification_type_id smallint(4) unsigned NOT NULL DEFAULT 0,
  item_id int(10) unsigned NOT NULL DEFAULT 0,
  item_parent_id int(10) unsigned NOT NULL DEFAULT 0,
  user_id int(10) unsigned NOT NULL DEFAULT 0,
  PRIMARY KEY (notification_type_id,item_id,item_parent_id,user_id)
);
insert into t1 values (1,1,1,1), (2,2,2,2), (3,3,3,3);
insert into t1 select seq,seq,seq,seq from seq_10_to_30;

let $consts=`select group_concat(concat("'",seq,"'")) from seq_1_to_4642`;

--echo # Run crashing query
--disable_query_log
eval
explain
DELETE FROM t1
WHERE
  notification_type_id IN (3, 4, 5, 6, 23)
  AND
  user_id = '5044'
  AND
  item_parent_id IN ($consts)
;
--enable_query_log

drop table t1;

--echo #
--echo # MDEV-25069: Assertion `root->weight >= ...' failed in SEL_ARG::tree_delete #2
--echo #

SELECT *
FROM mysql.help_relation
WHERE
  (help_topic_id < '2' OR help_topic_id != 8 OR help_topic_id < 1) AND
  help_keyword_id = help_topic_id;

--echo #
--echo # MDEV-29242: Assertion `computed_weight == weight' failed SEL_ARG::verify_weight
--echo #
CREATE TABLE t1 (id INT, KEY (id));
INSERT INTO t1 VALUES (1),(5);
SELECT id FROM t1 WHERE id IS NULL OR id NOT BETWEEN 1 AND 4;
DROP TABLE t1;