pingcap / pingcap/tidb

wrong estimation causing wrong plan in TPCC

Open
#39,519 0 comments 0 reactions 0 assignees View on GitHub
epic/cardinality-estimation sig/planner type/enhancement
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)

![7e0a38bd-6f61-4daa-a1d4-762ba666d2b3](https://user-images.githubusercontent.com/7499936/204843923-a00bce82-b1b7-45a7-b32e-499d5e6cd193.jpeg)

![7e7dfa95-21c7-4e29-8248-25f82f1724a2](https://user-images.githubusercontent.com/7499936/204843937-24dccc0b-609a-436c-abff-5ba0710d13f0.jpeg)

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

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

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

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the two reproduction images attached to issue #39519; the issue does not name any files, tests, TiDB version, expected result, or observed result. Recover a reproducible TPCC case, identify the planner estimation path involved, and verify that the resulting plan matches the expected behavior.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.