planner: fix TiDB server panic when uses indexMerge with the virtual generated column (#17065) #17126
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: sre-bot <sre-bot@pingcap.com>
|
/run-all-tests |
ghost
requested review from
wshwsh12,
winoros and
a team
and removed request for
a team
lzmhhh123
requested review from
wjhuang2016
and removed request for
wjhuang2016 and
lzmhhh123
zz-jason
added
status/can-merge
|
Your auto merge job has been accepted, waiting for:
|
|
/run-all-tests |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cherry-pick #17065 to release-4.0
What problem does this PR solve?
Issue Number: close #17045
Problem Summary:
Previously, we didn't consider index merge when implemented the virtual generated column.
What is changed and how it works?
Related changes
Check List
Tests
Side effects
Release note