-
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
select for update statement can't got stmt-count-limit error #48411
Labels
affects-4.0
This bug affects 4.0.x versions.
affects-5.0
This bug affects 5.0.x versions.
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
affects-5.3
This bug affects 5.3.x versions.
affects-5.4
This bug affects 5.4.x versions.
affects-6.1
affects-6.5
affects-7.1
affects-7.5
severity/critical
sig/transaction
SIG:Transaction
type/bug
The issue is confirmed as a bug.
Comments
crazycs520
added
type/bug
The issue is confirmed as a bug.
affects-6.5
affects-7.5
labels
Nov 8, 2023
13 tasks
ti-chi-bot
bot
added
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-7.1
labels
Nov 8, 2023
crazycs520
added
affects-5.0
This bug affects 5.0.x versions.
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
affects-5.3
This bug affects 5.3.x versions.
affects-5.4
This bug affects 5.4.x versions.
affects-6.1
labels
Nov 8, 2023
ti-chi-bot
bot
removed
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
labels
Nov 8, 2023
crazycs520
added
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
affects-7.1
and removed
may-affects-6.1
may-affects-7.1
may-affects-5.4
This bug maybe affects 5.4.x versions.
labels
Nov 8, 2023
This was referenced Nov 8, 2023
This was referenced Nov 9, 2023
This was referenced Nov 9, 2023
This was referenced Dec 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-4.0
This bug affects 4.0.x versions.
affects-5.0
This bug affects 5.0.x versions.
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
affects-5.3
This bug affects 5.3.x versions.
affects-5.4
This bug affects 5.4.x versions.
affects-6.1
affects-6.5
affects-7.1
affects-7.5
severity/critical
sig/transaction
SIG:Transaction
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)
For minimum reproduce, the TiDB's configuration as follow:
Reproduce SQL:
2. What did you expect to see? (Required)
When execute
select * from t for update;
, should got error:3. What did you see instead (Required)
All SQL are executed successfully, but the finally select result are following, the user may think that the transaction has been partially committed.
But you can find an error log in TiDB log file:
4. What is your TiDB version? (Required)
master: 89ec3d3
The text was updated successfully, but these errors were encountered: