-
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
planner,executor: fix point get for update read panic on partition table #25537
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 09d576a
|
/merge |
/run-all-tests |
/run-all-tests |
1 similar comment
/run-all-tests |
/merge |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 01342a9
|
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.1 in PR #25552 |
/run-cherry-picker |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-4.0 in PR #26274 |
What problem does this PR solve?
Issue Number: close #25528
Problem Summary:
#21148 add an extra partition ID column for the select lock executor, the table reader can handle it, but I forget the point / batch point get executor.
What is changed and how it works?
What's Changed:
Do not convert to point get executor for that case.
I see #21148 is already cherry picked to 5.1 and it introduce this bug, so it's better to fix the bug quickly.
This fix is simplest.
How it Works:
Avoid generate point get executor for that case.
Related changes
Check List
Tests
Side effects
Release note
Fix a bug which is caused by prior bug fix PR