txn: add a variable to control whether to lock unchanged unique keys #44714
Labels
affects-6.5
affects-7.1
severity/major
sig/transaction
SIG:Transaction
type/bug
The issue is confirmed as a bug.
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.
The text was updated successfully, but these errors were encountered: