-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Invalid query result on a cached table #52755
Comments
@winoros These two queries use different query plans. When ignoring the index i1, a table full scan is applied, while using the index i1, an index scan is applied. |
Similar to this one: #20007, |
/severity major |
/remove severity critical |
/remove-severity critical |
Long existing problem, and not common used cases. Adjust to major severity. |
/sig planner |
/assign @yibin87 |
/remove-sig execution |
It's a planner issue, and I'm going to fix it. |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
The first query should also return {5,7}.
3. What did you see instead (Required)
The first query returns an empty result.
4. What is your TiDB version? (Required)
Release Version: v8.0.0
Edition: Community
Git Commit Hash: 8ba1fa4
Git Branch: HEAD
UTC Build Time: 2024-03-28 14:22:15
GoVersion: go1.21.4
Race Enabled: false
Check Table Before Drop: false
Store: tikv
The text was updated successfully, but these errors were encountered: