-
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
binlog column mismatch when delete in pessimistic transaction #28292
Labels
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
severity/major
sig/sql-infra
SIG: SQL Infra
type/bug
The issue is confirmed as a bug.
Comments
Closed
12 tasks
Merged
12 tasks
it seems list partition table also has this problem when binlog enabled:
|
Exactly! This bug affects a lot of cases. |
Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label. |
This was referenced Dec 13, 2021
jebter
added
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
labels
Jan 18, 2022
How to deal with this problem? Will the latest version deal with this problem |
FYI this issue also affects v4.0.16 AFAIK this is only fixed on v5.3.0 onwards? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
severity/major
sig/sql-infra
SIG: SQL Infra
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
First found from a user https://asktug.com/t/topic/153774/13
Trigger condition:
Reproduce in UT, add this to
sessionctx/binloginfo/binloginfo_test.go
2. What did you expect to see? (Required)
No error
3. What did you see instead (Required)
It should be caused by #26373
The mismatched column might be the additional
ExtraPidColumn
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: