Skip to content

planner: not use the latest schema when plan-cache is off (#30959)#40046

Merged
ti-chi-bot merged 4 commits into
pingcap:release-5.1from
ti-chi-bot:cherry-pick-30959-to-release-5.1
Dec 19, 2022
Merged

planner: not use the latest schema when plan-cache is off (#30959)#40046
ti-chi-bot merged 4 commits into
pingcap:release-5.1from
ti-chi-bot:cherry-pick-30959-to-release-5.1

Conversation

@ti-chi-bot
Copy link
Copy Markdown
Member

This is an automated cherry-pick of #30959

Signed-off-by: you06 you1474600@gmail.com

What problem does this PR solve?

Issue Number: close #30940

Problem Summary:

What is changed and how it works?

Execute statements may use different schemas in building plan and execution, this issue is fixed in master by #26759, but hard to cherry-pick to 5.0 branch. Since plan cache is an experimental feature in 5.0, this PR skips fetching the latest schema for non-plan-cache statements.

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

fix a bug that concurrent DML and DDL may cause panic.

Signed-off-by: you06 <you1474600@gmail.com>
Signed-off-by: you06 <you1474600@gmail.com>
Signed-off-by: you06 <you1474600@gmail.com>
@ti-chi-bot
Copy link
Copy Markdown
Member Author

ti-chi-bot commented Dec 19, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • AilinKid
  • MyonKeminta
  • cfzjywxk

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.

Details

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 added cherry-pick-approved Cherry pick PR approved by release team. release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/cherry-pick-not-approved require-LGT3 Indicates that the PR requires three LGTM. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-5.1 and removed do-not-merge/cherry-pick-not-approved labels Dec 19, 2022
Copy link
Copy Markdown
Contributor

@AilinKid AilinKid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Dec 19, 2022
@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 Dec 19, 2022
@you06
Copy link
Copy Markdown
Contributor

you06 commented Dec 19, 2022

/cherry-pick-invite

Signed-off-by: AilinKid <314806019@qq.com>
@you06
Copy link
Copy Markdown
Contributor

you06 commented Dec 19, 2022

/merge

@ti-chi-bot
Copy link
Copy Markdown
Member Author

@you06: /merge is only allowed for the committers, you can assign this pull request to the committer in list by filling /assign @committer in the comment to help merge this pull request.

Details

In response to this:

/merge

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@AilinKid
Copy link
Copy Markdown
Contributor

/merge

@ti-chi-bot
Copy link
Copy Markdown
Member Author

@AilinKid: /merge in this pull request requires 3 approval(s).

Details

In response to this:

/merge

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@ti-chi-bot
Copy link
Copy Markdown
Member Author

@you06: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@ti-chi-bot ti-chi-bot added status/LGT3 The PR has already had 3 LGTM. and removed status/LGT2 Indicates that a PR has LGTM 2. labels Dec 19, 2022
@MyonKeminta
Copy link
Copy Markdown
Contributor

/merge

@ti-chi-bot
Copy link
Copy Markdown
Member Author

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

DetailsCommit hash: d2c711f

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Dec 19, 2022
@ti-chi-bot ti-chi-bot merged commit 48145ba into pingcap:release-5.1 Dec 19, 2022
@ti-chi-bot ti-chi-bot deleted the cherry-pick-30959-to-release-5.1 branch April 15, 2025 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cherry-pick-approved Cherry pick PR approved by release team. release-note Denotes a PR that will be considered when it comes time to generate release notes. require-LGT3 Indicates that the PR requires three LGTM. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT3 The PR has already had 3 LGTM. type/cherry-pick-for-release-5.1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants