pingcap / pingcap/tidb

data anomalies for pessimistic transactions

Open
#41,714 1 comment 0 reactions 0 assignees View on GitHub
sig/transaction type/question
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)

I ran the same histroy by both optimistic and pessimistic transactions, but got different results.

Optimistic transaction:

![image](https://user-images.githubusercontent.com/24265849/221086253-7418d13b-e2fe-4e30-91ec-db6ba37a4263.png)

Pessimistic transaction:

![image](https://user-images.githubusercontent.com/24265849/221086294-fbff0aa2-dd19-42be-9c6a-d743b88047a6.png)

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

One of the pessimistic transactions should be aborted. The results for the same history ran by optimistic and pessimistic transactions should be consistent.

### 3. What did you see instead (Required)

The results for the same history ran by optimistic and pessimistic transactions are different. All pessimistic transactions are committed successfully and the mistaken final values for each row entry indicate the data anomaly.

### 4. What is your TiDB version? (Required)

v5.4.0

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.