client-rust
client-rust copied to clipboard
n what situations will TiKV return a write conflict error when using pessimistic transactions?
Doesn't TiKV acquire a lock on the key in pessimistic transactions? Why would a write conflict error still occur?
get_for_update/batch_get_for_update if you want lock the key while query. Can you provide a minimum reproducible code snippet?