-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
tidb panic while query a table which was set collation #23506
Comments
/assign |
It's related to the collation decode. Assign to @xiongjiwei |
/assign @xiongjiwei |
it happens because we assume all the string to compare is valid utf8, but it is not true, it may be a binary charset. MySQL does fix this issue will cause performance regression |
@wjhuang2016 PTAL |
Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label. |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
new_collations_enabled_on_first_bootstrap = true
2. What did you expect to see? (Required)
execute successfully and TIDB not panic
3. What did you see instead (Required)
tidb log:
4. What is your TiDB version? (Required)
master: 1cebae2
release-5.0: 7ce49da
release-4.0: 11a9254
The text was updated successfully, but these errors were encountered: