pingcap / pingcap/tidb

transaction reports error

Open
#69,872 2 comments 0 reactions 0 assignees View on GitHub
contribution may-affects-7.5 may-affects-8.1 may-affects-8.5 severity/major sig/transaction type/bug
Dominant language
Go
Stars
40.5k
Forks
6.2k
PR merge metrics
PR metrics pending

Description

## Bug Report

Please answer these questions before submitting your issue. Thanks!

### 1. Minimal reproduce step (Required)
[S0] means executing in session 1, [S1] means executing in session 2

```sql
[S0] create table t0(c0 numeric zerofill unique );
[S0] insert ignore into t0(c0) values (-123604542) on duplicate key update c0='';
[S0] transaction:
[S0] BEGIN PESSIMISTIC;
[S0] UPDATE t0 SET c0 = c0 + 3 WHERE (NOT (t0.c0));
[S1] BEGIN
[S1] INSERT IGNORE INTO t0(c0) VALUES (-677996887), (841229591), (-1089449278);
[S0] BEGIN PESSIMISTIC;
-- ERROR 1105 (HY000): tikv aborts txn: pessimistic lock not found
```

### 2. What did you expect to see? (Required)
no error

### 3. What did you see instead (Required)
-- ERROR 1105 (HY000): tikv aborts txn: pessimistic lock not found

### 4. What is your TiDB version? (Required)
8.0.11-TiDB-v9.0.0-beta.1.pre-640-g24903d6b24-dirty

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Start by reproducing the two-session SQL sequence and trace the pessimistic transaction path around the TiKV "pessimistic lock not found" error; done means the sequence completes without an error and has regression coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, sql
Domain
databases, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.