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
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
|
# The block size influence cost estimates in JSON EXPLAIN.
# To produce the same cost estimates this test can only run with 16K pages.
#
# Default values for cost constants (from the source code)
#
let $row_evaluate_cost= 0.1;
let $key_compare_cost= 0.05;
let $memory_temptable_create_cost= 1.0;
let $memory_temptable_row_cost= 0.1;
let $disk_temptable_create_cost= 20;
let $disk_temptable_row_cost= 0.5;
let $memory_block_read_cost= 0.25;
let $io_block_read_cost= 1.0;
--echo #
--echo # Bug#20443863 USE OF WORST_SEEKS IN FIND_BEST_REF() CAN LEAD TO
--echo # WRONG QUERY PLAN
--echo #
CREATE TABLE t1 (
i1 INTEGER,
i2 INTEGER,
i3 INTEGER,
KEY(i1,i2)
) ENGINE=InnoDB;
INSERT INTO t1 VALUES (1, 1, 1), (1, 1, 1),(1, 1, 1),(1, 1, 1),
(2, 2, 1), (2, 2, 1),(2, 2, 1),(2, 2, 1),
(3, 3, 1), (3, 3, 1),(3, 3, 1),(3, 3, 1);
--disable_query_log
--disable_result_log
ANALYZE TABLE t1;
--enable_result_log
--enable_query_log
# worst_seeks is used for two cases: when the entire index is used and
# when only a prefix of the index is used. Two get coverage for both cases,
# two almost identical queries are needed.
# Test query for case 1: the entire index is used
let query_1= SELECT i3 FROM t1 WHERE i1 = 1 AND i2 = 1;
# Test query for case 2: only a prefix of the index is used
let query_2= SELECT i3 FROM t1 WHERE i1 = 1 AND i3 = 1;
# Run the queries with default cost constants
# Create a user connection
connect (con1,localhost,root,,);
# Get cost estimates with default values
--skip_if_hypergraph # Depends on the query plan.
eval EXPLAIN FORMAT=JSON $query_1;
--skip_if_hypergraph # Depends on the query plan.
eval EXPLAIN FORMAT=JSON $query_2;
disconnect con1;
--source include/wait_until_disconnected.inc
connection default;
# Double the value that the cost constants have:
# 1. Replace the NULL in the cost_value column with actual value
# Update server_cost:
eval UPDATE mysql.server_cost
SET cost_value=$row_evaluate_cost
WHERE cost_name="row_evaluate_cost";
eval UPDATE mysql.server_cost
SET cost_value=$key_compare_cost
WHERE cost_name="key_compare_cost";
eval UPDATE mysql.server_cost
SET cost_value=$memory_temptable_create_cost
WHERE cost_name="memory_temptable_create_cost";
eval UPDATE mysql.server_cost
SET cost_value=$memory_temptable_row_cost
WHERE cost_name="memory_temptable_row_cost";
eval UPDATE mysql.server_cost
SET cost_value=$disk_temptable_create_cost
WHERE cost_name="disk_temptable_create_cost";
eval UPDATE mysql.server_cost
SET cost_value=$disk_temptable_row_cost
WHERE cost_name="disk_temptable_row_cost";
# Update engine_cost:
eval UPDATE mysql.engine_cost
SET cost_value=$memory_block_read_cost
WHERE cost_name="memory_block_read_cost";
eval UPDATE mysql.engine_cost
SET cost_value=$io_block_read_cost
WHERE cost_name="io_block_read_cost";
# 2. Multiply all cost constants by two
UPDATE mysql.server_cost
SET cost_value = 2 * cost_value;
UPDATE mysql.engine_cost
SET cost_value = 2 * cost_value;
# Validate cost constants
SELECT cost_name, cost_value FROM mysql.server_cost;
SELECT cost_name, cost_value FROM mysql.engine_cost;
FLUSH OPTIMIZER_COSTS;
# Re-run the queries with the new cost constants
# Create a user connection
connect (con1,localhost,root,,);
# The new cost estimates should be approximately the double compared to the
# first run
--skip_if_hypergraph # Depends on the query plan.
eval EXPLAIN FORMAT=JSON $query_1;
--skip_if_hypergraph # Depends on the query plan.
eval EXPLAIN FORMAT=JSON $query_2;
disconnect con1;
--source include/wait_until_disconnected.inc
connection default;
# Reset cost constants
UPDATE mysql.server_cost
SET cost_value=DEFAULT;
UPDATE mysql.engine_cost
SET cost_value=DEFAULT;
FLUSH OPTIMIZER_COSTS;
DROP TABLE t1;
--echo #
--echo # Bug#20947871 INDEX SCAN COST IN TEST_IF_CHEAPER_ORDERING() DOES
--echo # NOT USE COST CONSTANTS
--echo #
CREATE TABLE t1 (
pk INTEGER PRIMARY KEY,
a INTEGER,
b INTEGER,
c CHAR(255),
UNIQUE KEY k1 (a)
);
INSERT INTO t1 VALUES (1, 1, NULL, "Abc"), (2, 2, NULL, "Abc"),
(3, 3, NULL, "Abc"), (4, 4, NULL, "Abc");
INSERT INTO t1 SELECT a + 4, a + 4, b, c FROM t1;
INSERT INTO t1 SELECT a + 8, a + 8, b, c FROM t1;
INSERT INTO t1 SELECT a + 16, a + 16, b, c FROM t1;
INSERT INTO t1 SELECT a + 32, a + 32, b, c FROM t1;
INSERT INTO t1 SELECT a + 64, a + 64, b, c FROM t1;
INSERT INTO t1 SELECT a + 128, a + 128, b, c FROM t1;
CREATE TABLE t2 (
d INTEGER PRIMARY KEY,
e INTEGER
);
INSERT INTO t2 SELECT a, b FROM t1;
--disable_query_log
--disable_result_log
ANALYZE TABLE t1, t2;
--enable_result_log
--enable_query_log
# Test query: This should do limit optimization and use index without filesort
let query= SELECT * FROM t1 JOIN t2 ON b=d ORDER BY a LIMIT 4;
# Run the query with default cost constants
# Create a user connection
connect (con1,localhost,root,,);
# Get cost estimates with default values
--echo # Query should be optimized for the LIMIT. Query plan should
--echo # use index without filesort
--skip_if_hypergraph # Depends on the query plan.
eval EXPLAIN FORMAT=JSON $query;
disconnect con1;
--source include/wait_until_disconnected.inc
connection default;
# Halve the value of the cost constants:
# 1. Replace the NULL in the cost_value column with actual value
# Update server_cost:
eval UPDATE mysql.server_cost
SET cost_value=$row_evaluate_cost
WHERE cost_name="row_evaluate_cost";
eval UPDATE mysql.server_cost
SET cost_value=$key_compare_cost
WHERE cost_name="key_compare_cost";
eval UPDATE mysql.server_cost
SET cost_value=$memory_temptable_create_cost
WHERE cost_name="memory_temptable_create_cost";
eval UPDATE mysql.server_cost
SET cost_value=$memory_temptable_row_cost
WHERE cost_name="memory_temptable_row_cost";
eval UPDATE mysql.server_cost
SET cost_value=$disk_temptable_create_cost
WHERE cost_name="disk_temptable_create_cost";
eval UPDATE mysql.server_cost
SET cost_value=$disk_temptable_row_cost
WHERE cost_name="disk_temptable_row_cost";
# Update engine_cost:
eval UPDATE mysql.engine_cost
SET cost_value=$memory_block_read_cost
WHERE cost_name="memory_block_read_cost";
eval UPDATE mysql.engine_cost
SET cost_value=$io_block_read_cost
WHERE cost_name="io_block_read_cost";
# 2. Divide all cost constants by two
UPDATE mysql.server_cost
SET cost_value = 0.5 * cost_value;
UPDATE mysql.engine_cost
SET cost_value = 0.5 * cost_value;
# Validate cost constants
SELECT cost_name, cost_value FROM mysql.server_cost;
SELECT cost_name, cost_value FROM mysql.engine_cost;
FLUSH OPTIMIZER_COSTS;
# Re-run the queries with the new cost constants
# Create a user connection
connect (con1,localhost,root,,);
# The new cost estimates should be approximately half compared to the
# first run. The query plan should still be the same.
--echo # This should be optimized for the LIMIT. Query plan should
--echo # use index without filesort
--skip_if_hypergraph # Depends on the query plan.
eval EXPLAIN FORMAT=JSON $query;
disconnect con1;
--source include/wait_until_disconnected.inc
connection default;
# Reset cost constants
UPDATE mysql.server_cost
SET cost_value=DEFAULT;
UPDATE mysql.engine_cost
SET cost_value=DEFAULT;
FLUSH OPTIMIZER_COSTS;
DROP TABLE t1, t2;
|
