Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RANGE COLUMNS partitioning pruning includes an impossible partition #42273

Closed
mjonss opened this issue Mar 15, 2023 · 2 comments · Fixed by #42356
Closed

RANGE COLUMNS partitioning pruning includes an impossible partition #42273

mjonss opened this issue Mar 15, 2023 · 2 comments · Fixed by #42356
Assignees
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.0 affects-7.1 This bug affects the 7.1.x(LTS) versions. component/tablepartition This issue is related to Table Partition of TiDB. severity/major sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.

Comments

@mjonss
Copy link
Contributor

mjonss commented Mar 15, 2023

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

CREATE TABLE t
(a tinyint unsigned,
 b tinyint unsigned)
PARTITION BY RANGE COLUMNS (a,b)
(PARTITION p0 VALUES LESS THAN (10,255),
 PARTITION p1 VALUES LESS THAN (11,MAXVALUE),
 PARTITION p2 VALUES LESS THAN (MAXVALUE,1));
explain select * from t where a = 11;
analyze table t; -- Enables dynamic prune mode
explain select * from t where a = 11;

2. What did you expect to see? (Required)

Only partition p1 should be included, like MySQL:

mysql> CREATE TABLE t
    -> (a tinyint unsigned,
    ->  b tinyint unsigned)
    -> PARTITION BY RANGE COLUMNS (a,b)
    -> (PARTITION p0 VALUES LESS THAN (10,255),
    ->  PARTITION p1 VALUES LESS THAN (11,MAXVALUE),
    ->  PARTITION p2 VALUES LESS THAN (MAXVALUE,1));
Query OK, 0 rows affected (0,03 sec)

mysql> explain select * from t where a = 11;
+----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+-------------+
| id | select_type | table | partitions | type | possible_keys | key  | key_len | ref  | rows | filtered | Extra       |
+----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+-------------+
|  1 | SIMPLE      | t     | p1         | ALL  | NULL          | NULL | NULL    | NULL |    1 |   100.00 | Using where |
+----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+-------------+
1 row in set, 1 warning (0,00 sec)

3. What did you see instead (Required)

Partition p2 is included, when it cannot hold any values where a = 11.

tidb> CREATE TABLE t
    -> (a tinyint unsigned,
    ->  b tinyint unsigned)
    -> PARTITION BY RANGE COLUMNS (a,b)
    -> (PARTITION p0 VALUES LESS THAN (10,255),
    ->  PARTITION p1 VALUES LESS THAN (11,MAXVALUE),
    ->  PARTITION p2 VALUES LESS THAN (MAXVALUE,1));
Query OK, 0 rows affected (0.08 sec)

tidb> explain select * from t where a = 11;
+-----------------------------+----------+-----------+-----------------------+--------------------------------+
| id                          | estRows  | task      | access object         | operator info                  |
+-----------------------------+----------+-----------+-----------------------+--------------------------------+
| PartitionUnion_8            | 20.00    | root      |                       |                                |
| ├─TableReader_11        | 10.00    | root      |                       | data:Selection_10              |
| │ └─Selection_10      | 10.00    | cop[tikv] |                       | eq(test.t.a, 11)               |
| │   └─TableFullScan_9 | 10000.00 | cop[tikv] | table:t, partition:p1 | keep order:false, stats:pseudo |
| └─TableReader_14        | 10.00    | root      |                       | data:Selection_13              |
|   └─Selection_13        | 10.00    | cop[tikv] |                       | eq(test.t.a, 11)               |
|     └─TableFullScan_12  | 10000.00 | cop[tikv] | table:t, partition:p2 | keep order:false, stats:pseudo |
+-----------------------------+----------+-----------+-----------------------+--------------------------------+
7 rows in set, 1 warning (0.00 sec)

tidb> analyze table t; -- Enables dynamic prune mode
Query OK, 0 rows affected, 6 warnings (0.15 sec)

tidb> explain select * from t where a = 11;
+-------------------------+----------+-----------+-----------------+--------------------------------+
| id                      | estRows  | task      | access object   | operator info                  |
+-------------------------+----------+-----------+-----------------+--------------------------------+
| TableReader_7           | 10.00    | root      | partition:p1,p2 | data:Selection_6               |
| └─Selection_6       | 10.00    | cop[tikv] |                 | eq(test.t.a, 11)               |
|   └─TableFullScan_5 | 10000.00 | cop[tikv] | table:t         | keep order:false, stats:pseudo |
+-------------------------+----------+-----------+-----------------+--------------------------------+
3 rows in set (0.00 sec)

4. What is your TiDB version? (Required)

tidb_version(): Release Version: v6.6.0
Edition: Community
Git Commit Hash: f4ca0821fb96a2bdd37d2fb97eb26c07fc58d4e4
Git Branch: heads/refs/tags/v6.6.0
UTC Build Time: 2023-02-17 14:39:38
GoVersion: go1.19.5
Race Enabled: false
TiKV Min Version: 6.2.0-alpha
Check Table Before Drop: false
Store: tikv
@mjonss mjonss added the type/bug The issue is confirmed as a bug. label Mar 15, 2023
@shiyuhang0
Copy link
Member

I don't have time now. But I want to try it if no one solves it after 1-2 weeks

@jebter jebter added sig/sql-infra SIG: SQL Infra component/tablepartition This issue is related to Table Partition of TiDB. severity/major labels Mar 16, 2023
@ti-chi-bot ti-chi-bot added may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 labels Mar 16, 2023
@mjonss
Copy link
Contributor Author

mjonss commented Mar 16, 2023

I do not consider it to be a major, but rather a minor severity, since it is still giving correct result, just not optmized, since it may scan one more partition in this edge case.

@mjonss mjonss added affects-6.5 This bug affects the 6.5.x(LTS) versions. and removed may-affects-6.5 may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-6.1 labels Apr 6, 2023
@VelocityLight VelocityLight added the affects-7.1 This bug affects the 7.1.x(LTS) versions. label Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.0 affects-7.1 This bug affects the 7.1.x(LTS) versions. component/tablepartition This issue is related to Table Partition of TiDB. severity/major sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants