pingcap / pingcap/tidb

wrongly enable plan cache with tiflash

Open
#60,984 2 comments 0 reactions 1 assignee Claimed by @time-and-fate View on GitHub
affects-6.1 affects-6.5 report/customer severity/minor 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)

```
tiup playground v6.5.10 --host 0.0.0.0 --db 1 --kv 1 --pd 1 --tiflash 1

plan replayer load 'replay0416.zip';

set tidb_slow_log_threshold=0;

use sz_online_kyc;

PREPARE STMT FROM "SELECT
C1.TXN_REQNO,
C1.SRC_SYS,
C2.LISTID AS AML_FCS_NMLST_TP,
C1.REQ_SN,
C1.BLIST_MODER_NAME,
C1.BLIST_MODER_ADDR,
C1.BLIST_MODER_CRDT,
C1.BLIST_MODER_BIRT,
C1.COMP,
C1.BLIST_RCRD_NO,
C1.HIT_KYWRD,
C2.LISTNAME
FROM
CASE_NAMELIST_HIT_DETAIL C1
INNER JOIN (
SELECT
MAX(C.SN) SN,
C.BLIST_RCRD_NO,
C.COMP,
M.LISTID,
M.LISTNAME
FROM
CASE_NAMELIST_HIT_DETAIL C
INNER JOIN (
SELECT
BLIST_RCRD_NO,
MAX(COMP) COMP,
GROUP_CONCAT(DISTINCT C.AML_FCS_NMLST_TP) LISTID,
GROUP_CONCAT(DISTINCT S.LISTNAME) LISTNAME
FROM
CASE_NAMELIST_HIT_DETAIL C
LEFT JOIN SZ_ONLINE_COM.SYS_LIST_CONFIG S ON C.AML_FCS_NMLST_TP = S.LISTID
WHERE
C.CASE_REFNO = ?
GROUP BY
BLIST_RCRD_NO
) M
WHERE
C.COMP = M.COMP
AND C.BLIST_RCRD_NO = M.BLIST_RCRD_NO
AND C.CASE_REFNO = ?
GROUP BY
C.BLIST_RCRD_NO,
C.COMP,
M.LISTID,
M.LISTNAME
) C2 ON C1.SN = C2.SN
WHERE
C1.CASE_REFNO = ?
ORDER BY
C1.COMP DESC,
C1.SN DESC";

set @a='003CLS250416000002025',@b='003CLS250416000002025',@c='003CLS250416000002025';

execute STMT using @a,@b,@c;

set @a='003CLS250416000004144',@b='003CLS250416000004144',@c='003CLS250416000004144';

execute STMT using @a,@b,@c;

select @@last_plan_from_cache;
返回为 1
```

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

cannot use the plan cache
### 3. What did you see instead (Required)

use the plan cache
### 4. What is your TiDB version? (Required)
v6.5.10

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.