pingcap / pingcap/tidb

`execution info` in slow query is not accurate

Open
#49,026 2 comments 0 reactions 0 assignees View on GitHub
severity/moderate sig/diagnosis sig/execution 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)
1. create a cluster version v6.5.3
2. prepare one 100 rows sysbench table `sysbench --config-file=config oltp_update_index --tables=1 --table_size=100 --threads=100 prepare`
3. modify the update query to like `UPDATE sbtest1 SET k = k + 1 WHERE id > ? - 10 ;`
4. run the benchmark with table_size = 1 to make the query stable `sysbench --config-file=config oltp_update_index --tables=1 --table_size=1 --threads=100 run`

### 2. What did you expect to see? (Required)
actRows == total_process_keys && total_process_keys == process_keys

### 3. What did you see instead (Required)
Screenshot 2023-11-30 at 11 49 40
All the three values are different. The process_keys may only contain one time execution info.

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

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.