-
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
SET GLOBAL tidb_skip_isolation_level_check=1 doesn't work as expected #27897
Comments
I commented on the PR, but I'm not sure this is a bug. GLOBAL scoped changes are not supposed to apply to the current session yet. They only apply to new sessions. |
Oops, you are right. I agree that global changes should not affect current session. However I saw something strange that there might be some other issue as well. The first time I restart client to check global variables and change isolation level to I will take another look to this. |
After checking comments in PR, I realized that you already pointed out the root cause. My last experiment failed because I didn't read variable to force reload from global before changing isolation level. Simply remove skipInit from |
Please check whether the issue should be labeled with 'affects-x.y' or 'backport-x.y.z', |
/label affects-5.1 |
@sunxiaoguang: The label(s) 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. |
/label affects-5.2 |
@sunxiaoguang: The label(s) 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. |
/label needs-cherry-pick-5.1 |
/label needs-cherry-pick-5.2 |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Disconnect and reconnect to TiDB
2. What did you expect to see? (Required)
Disconnect and reconnect to TiDB
3. What did you see instead (Required)
Disconnect and reconnect to TiDB
4. What is your TiDB version? (Required)
5.1.0 and all the new versions
The text was updated successfully, but these errors were encountered: