optimize the list partition pruner for range query, #22144
Labels
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
type/performance
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduction step (Required)
For the list partition table:
Currently, range query can't prune partition:
But actually, we can use
id < 3
to do partition prune, since only partitionp0
contain the value thatid<3
. The expected result is:Idea
Use a
BTree
to store the all list partition values, for range query, traversal the range to find the partition in this range.Samely,
the list column partition
can also use this optimization.4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: