planner: fix bug caused by wrong column indice in NominalSort's sort item (#31324) #31500
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 #31324 to release-5.2
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/31500
After apply modifications, you can push your change to this PR via:
Signed-off-by: guo-shaoge shaoge1994@163.com
What problem does this PR solve?
Issue Number: close #31035
Problem Summary: TiDB panic because column indice is wrong.
COL2 + 9843176
,COL2
's indice is wrong, it should be 1, but we got 0.InjectExtraProjection
(*defaultEvaluator).run
, we use the wrong col index(0) to evaluateCOL2 + 9843176
.(col index 0 is text type, but col2 is decimal, that's why tidb panic when decode mydecimal)What is changed and how it works?
Also resolve indice for NominalSort.
Check List
Tests
Side effects
Documentation
Release note