sessionctx: fix the value of analyze_version when upgrading 4.x to 5.… (#30743)#30752
sessionctx: fix the value of analyze_version when upgrading 4.x to 5.… (#30743)#30752ti-srebot wants to merge 1 commit into
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
[REVIEW NOTIFICATION] This pull request has not been approved. 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. DetailsReviewer can indicate their review by submitting an approval review. |
|
@ti-srebot: This cherry pick PR is for a release branch and has not yet been approved by release team. To merge this cherry pick, it must first be approved by the collaborators. AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review. DetailsInstructions 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 kubernetes/test-infra repository. |
|
/run-all-tests |
|
@winoros you're already a collaborator in bot's repo. |
|
This pull request is closed because it's related version has closed automatic cherry-picking. You can find more details at: |
cherry-pick #30743 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/30752After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #25422
Problem Summary:
Use the same way with #30650
What is changed and how it works?
When do upgrading, we first check whether the variable exists.
If not exist, we use the
1which is the old behavior in 4.0 and before.Check List
Tests
Documentation
Release note