Skip to content
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.

Sign up for GitHub

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

Jump to bottom

planner: fix prepare explain index out of range bug (#40568) #40602

Merged
merged 5 commits into from
Jan 17, 2023
Merged

planner: fix prepare explain index out of range bug (#40568) #40602

merged 5 commits into from
Jan 17, 2023

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #40568

What problem does this PR solve?

Issue Number: close #38323

Problem Summary:

What is changed and how it works?

The ParamMarker in Constant should be nil when execute prepare sql, we don't need parameter in this stage.

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No code

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

@fzzf678 @ti-chi-bot
This is an automated cherry-pick of pingcap#40568
16a249e 
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot
Copy link
Member Author

ti-chi-bot commented Jan 16, 2023 •
edited
Loading

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • Reminiscent
  • qw4990

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot mentioned this pull request Jan 16, 2023
Merged
12 tasks
@ti-chi-bot ti-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/cherry-pick-not-approved epic/plan-cache sig/planner SIG: Planner size/S Denotes a PR that changes 10-29 lines, ignoring generated files. type/bugfix This PR fixes a bug. type/cherry-pick-for-release-6.1 This PR is cherry-picked to release-6.1 from a source PR. labels Jan 16, 2023
@VelocityLight VelocityLight added the cherry-pick-approved Cherry pick PR approved by release team. label Jan 16, 2023
@ti-chi-bot ti-chi-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed do-not-merge/cherry-pick-not-approved size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jan 16, 2023
@fzzf678
Copy link
Contributor

fzzf678 commented Jan 16, 2023

cherry-pick-invite

@fzzf678
Copy link
Contributor

fzzf678 commented Jan 16, 2023

/cherry-pick-invite

@ti-chi-bot
Copy link
Member Author

@fzzf678 you're already a collaborator in repo ti-chi-bot/tidb

@ti-chi-bot ti-chi-bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 16, 2023
@fzzf678
Copy link
Contributor

fzzf678 commented Jan 16, 2023

/test check-dev

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Jan 16, 2023
@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Jan 16, 2023
@chrysan
Copy link
Contributor

chrysan commented Jan 16, 2023

/run-check_dev

@fzzf678
Copy link
Contributor

fzzf678 commented Jan 16, 2023

/test check-dev

@qw4990
Copy link
Contributor

qw4990 commented Jan 17, 2023

/merge

@ti-chi-bot
Copy link
Member Author

This pull request has been accepted and is ready to merge.

Commit hash: 8cd3802

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Jan 17, 2023
@qw4990
Copy link
Contributor

qw4990 commented Jan 17, 2023

/test unit-test

1 similar comment
@Ivy-YinSu
Copy link

/test unit-test

@ti-chi-bot ti-chi-bot merged commit dd5ff49 into pingcap:release-6.1 Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Reminiscent Reminiscent Reminiscent approved these changes

@qw4990 qw4990 qw4990 approved these changes

Assignees

@fzzf678 fzzf678

Labels
cherry-pick-approved Cherry pick PR approved by release team. epic/plan-cache release-note-none Denotes a PR that doesn't merit a release note. sig/planner SIG: Planner size/S Denotes a PR that changes 10-29 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/bugfix This PR fixes a bug. type/cherry-pick-for-release-6.1 This PR is cherry-picked to release-6.1 from a source PR.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
7 participants
@ti-chi-bot @fzzf678 @chrysan @qw4990 @Ivy-YinSu @Reminiscent @VelocityLight