-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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: fix panic when prepare and execute the insert on duplicate #37924
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. |
planner/core/planbuilder.go
Outdated
@@ -3821,13 +3821,13 @@ func (b *PlanBuilder) buildSelectPlanOfInsert(ctx context.Context, insert *ast.I | |||
if err != nil { | |||
return err | |||
} | |||
actualColLen := -1 | |||
actualColLen := insert.ColLen |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because the initialization value for insert.ColLen
is 0. And it's impossible for the variable actualColLen
's end value be zero(I guess. In code, it will be assigned to actualColLen = selectPlan.Schema().Len()
). So we change the actualColLen
's initiation value to 0.
planner/core/planbuilder.go
Outdated
@@ -3821,13 +3821,13 @@ func (b *PlanBuilder) buildSelectPlanOfInsert(ctx context.Context, insert *ast.I | |||
if err != nil { | |||
return err | |||
} | |||
actualColLen := -1 | |||
actualColLen := insert.ColLen |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about adding some comments like see issue #37187 here
?
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 7af05a6
|
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.3 in PR #38102 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.4 in PR #38103 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-6.1 in PR #38104 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-6.3 in PR #38105 |
TiDB MergeCI notify✅ Well Done! New fixed [1] after this pr merged.
|
/run-cherry-picker |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
What problem does this PR solve?
Issue Number: close #37187
Problem Summary:
The prepare and execute statements both will build the plan. But some code path in
planBuilder
have some assumptions about they only execute once.What is changed and how it works?
actualColLen
inlast.InsertStmt
for reusing.actualColLen
to 0 not 1. Because it's safe and easy to handle.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.