Skip to content
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

txn: add a variable to control whether to lock unchanged unique keys #44714

Closed
ekexium opened this issue Jun 15, 2023 · 0 comments · Fixed by #44598
Closed

txn: add a variable to control whether to lock unchanged unique keys #44714

ekexium opened this issue Jun 15, 2023 · 0 comments · Fixed by #44598

Comments

@ekexium
Copy link
Contributor

ekexium commented Jun 15, 2023

Enhancement

#42210 and #42713 introduced the behavior of locking unchanged unique keys in INSERT IGNORE/REPLACE/UPDATE statements.
Locking more keys leads to higher TiKV load and a higher possibility of lock contention.
The performance impact may unexpectedly annoy performance-sensitive applications when they upgrade from an older version. We'd better add a switch to control the behavior.

@ti-chi-bot ti-chi-bot bot added may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. 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-6.5 labels Jun 15, 2023
@ekexium ekexium added affects-6.5 sig/transaction SIG:Transaction and removed may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. 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-6.5 type/enhancement labels Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant