pingcap / pingcap/tidb

plan change from tiflash full scan to index range scan when upgrade to next-gen

Open
#64,446 2 comments 0 reactions 0 assignees View on GitHub
sig/planner 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)

plan replayer load 'replayer_xm3nY3nWGx72UpQLxpyhyg==_1762947179758778588.zip';

since the below two plan is built from same stats, we should assume that the rows after all filters applied should be quite similar, but we can tell that the rows after all filter applied, is different among this two plan, that's means the count from `selection_48` of tiflash plan and the one from `selection_22` from index lookup plan, they differs.

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

![Image](https://github.com/user-attachments/assets/6e900e6f-a72c-4968-9a58-8db2e17e1889)

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

![Image](https://github.com/user-attachments/assets/375f3439-8ba5-4e2f-9a75-0040edd07f30)

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

next-gen and master

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.