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
|
#!/usr/bin/env tarantool
test = require("sqltester")
test:plan(14)
--!./tcltestrunner.lua
-- 2011 April 1
--
-- The author disclaims copyright to this source code. In place of
-- a legal notice, here is a blessing:
--
-- May you do good and not evil.
-- May you find forgiveness for yourself and forgive others.
-- May you share freely, never taking more than you give.
--
-------------------------------------------------------------------------
-- This file implements tests for the ANALYZE command when an idnex
-- name is given as the argument.
--
test:do_test(
"analyze7-1.0",
function()
return test:execsql([[
DROP TABLE IF EXISTS t1;
CREATE TABLE t1(id INT PRIMARY KEY, a INT , b INT , c INT , d INT );
CREATE INDEX t1a ON t1(a);
CREATE INDEX t1b ON t1(b);
CREATE INDEX t1cd ON t1(c, d);
DROP TABLE IF EXISTS nums;
CREATE TABLE nums(n INT PRIMARY KEY);
INSERT into nums WITH RECURSIVE cnt(x) AS (VALUES(1) UNION ALL SELECT x+1 FROM cnt WHERE x<256) SELECT x FROM cnt;
INSERT INTO t1 SELECT n, n, n, n/100, n FROM nums;
EXPLAIN QUERY PLAN SELECT * FROM t1 WHERE a=123;
]])
end, {
-- <analyze7-1.0>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1A (A=?)"
-- </analyze7-1.0>
})
test:do_execsql_test(
"analyze7-1.1",
[[
EXPLAIN QUERY PLAN SELECT * FROM t1 WHERE b=123;
]], {
-- <analyze7-1.1>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1B (B=?)"
-- </analyze7-1.1>
})
test:do_execsql_test(
"analyze7-1.2",
[[
EXPLAIN QUERY PLAN SELECT * FROM t1 WHERE c=2;
]], {
-- <analyze7-1.2>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1CD (C=?)"
-- </analyze7-1.2>
})
-- Run an analyze on one of the three indices. Verify that this
-- effects the row-count estimate on the one query that uses that
-- one index.
--
test:do_test(
"analyze7-2.0",
function()
test:execsql("ANALYZE;")
return test:execsql("EXPLAIN QUERY PLAN SELECT * FROM t1 WHERE a=123;")
end, {
-- <analyze7-2.0>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1A (A=?)"
-- </analyze7-2.0>
})
test:do_execsql_test(
"analyze7-2.1",
[[
EXPLAIN QUERY PLAN SELECT * FROM t1 WHERE b=123;
]], {
-- <analyze7-2.1>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1B (B=?)"
-- </analyze7-2.1>
})
test:do_execsql_test(
"analyze7-2.2",
[[
EXPLAIN QUERY PLAN SELECT * FROM t1 WHERE c=2;
]], {
-- <analyze7-2.2>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1CD (C=?)"
-- </analyze7-2.2>
})
-- Verify that since the query planner now things that t1a is more
-- selective than t1b, it prefers to use t1a.
-- Tarantool: can't run analyze on certain index, so just run global analyze and drop index.
test:do_execsql_test(
"analyze7-2.3",
[[
DROP INDEX t1b ON t1;
CREATE INDEX t1b ON t1(b);
EXPLAIN QUERY PLAN SELECT * FROM t1 WHERE a=123 AND b=123;
]], {
-- <analyze7-2.3>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1A (A=?)"
-- </analyze7-2.3>
})
-- Run an analysis on another of the three indices. Verify that this
-- new analysis works and does not disrupt the previous analysis.
--
test:do_test(
"analyze7-3.0",
function()
test:execsql("ANALYZE;")
return test:execsql("EXPLAIN QUERY PLAN SELECT * FROM t1 WHERE a=123;")
end, {
-- <analyze7-3.0>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1A (A=?)"
-- </analyze7-3.0>
})
test:do_execsql_test(
"analyze7-3.1",
[[
EXPLAIN QUERY PLAN SELECT * FROM t1 WHERE b=123;
]], {
-- <analyze7-3.1>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1B (B=?)"
-- </analyze7-3.1>
})
test:do_execsql_test(
"analyze7-3.2.1",
[[
EXPLAIN QUERY PLAN SELECT * FROM T1 WHERE C=?;
]], {
-- <analyze7-3.2.1>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1CD (C=?)"
-- </analyze7-3.2.1>
})
-- sql comes up with a different estimated
-- row count for (c=2) than it does for (c=?).
test:do_execsql_test(
"analyze7-3.2.2",
[[
EXPLAIN QUERY PLAN SELECT * FROM t1 WHERE c=2;
]], {
-- <analyze7-3.2.2>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1CD (C=?)"
-- </analyze7-3.2.2>
})
test:do_execsql_test(
"analyze7-3.3",
[[
EXPLAIN QUERY PLAN SELECT * FROM T1 WHERE A=123 AND B=123;
]], {
-- After running second ANALYZE query, there are equal statistics for
-- indexes t1a and t1b, so it doesn't really matter which index planner uses.
-- <analyze7-3.3>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1A (A=?)"
--0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1B (B=?)"
-- </analyze7-3.3>
})
test:do_execsql_test(
"analyze7-3.4",
[[
EXPLAIN QUERY PLAN SELECT * FROM t1 WHERE c=123 AND b=123;
]], {
-- <analyze7-3.4>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1CD (C=?)"
-- </analyze7-3.4>
})
test:do_execsql_test(
"analyze7-3.6",
[[
EXPLAIN QUERY PLAN SELECT * FROM t1 WHERE c=123 AND d=123 AND b=123;
]], {
-- <analyze7-3.6>
0, 0, 0, "SEARCH TABLE T1 USING COVERING INDEX T1CD (C=? AND D=?)"
-- </analyze7-3.6>
})
test:finish_test()
|
