txn: unexpected behavior for point-get and LOCK IN SHARE MODE
#52432
Labels
affects-6.1
affects-6.2
affects-6.3
affects-6.4
affects-6.5
affects-6.6
affects-7.0
affects-7.1
affects-7.2
affects-7.3
affects-7.4
affects-7.5
affects-7.6
affects-8.0
affects-8.1
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
severity/moderate
sig/transaction
SIG:Transaction
type/bug
This issue is a bug.
Bug Report
1. Minimal reproduce step (Required)
Using
LOCK IN SHARED MODE
in a point-get query:2. What did you expect to see? (Required)
According to TiDB document, TiDB should report an error using
SHARE IN LOCK MODE
whentidb_enable_noop_functions=OFF
.3. What did you see instead (Required)
4. What is your TiDB version? (Required)
All versions of TiDB have this issue, I believe.
5. Root cause analysis
Notice that for
select * from t where a=1 lock in share mode
, TiDB uses a 'fast path' for point-get, we didn't handleLOCK IN SHARE MODE
in this path.The text was updated successfully, but these errors were encountered: