Return more results than expected when executing SQL with prefix indexes #24356
Labels
cherry-pick-approved
Cherry pick PR approved by release team.
severity/critical
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
TiDB
MySQL
2. What did you expect to see? (Required)
a. Separate prefix index results are correct
b. The prefix index is not in the first position of the combined index, the result is also correct
c. The result is correct even if the prefix index is in the first position of the combined index, but the where only has the prefix index column
d. The prefix index must be in the first position of the combined index, and the where condition includes all combined index columns, the result is more than expected
Occasionally, errors occur in this case
3. What did you see instead (Required)
4. What is your TiDB version? (Required)
3.0.16、3.0.19、4.0.8、4.0.10、4.0.12、5.0.0
The text was updated successfully, but these errors were encountered: