Prepared statements results fails partition pruning if not PointGet #55630
Labels
affects-8.1
This bug affects the 8.1.x(LTS) versions.
component/tablepartition
This issue is related to Table Partition of TiDB.
severity/major
sig/sql-infra
SIG: SQL Infra
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Create a sysbench table
Create a similar table, but partitioned and copy the data from the table created by sysbench and finally rename to sbtest1
Run sysbench_random_ranges, note that sysbench is using prepared statements!
2. What did you expect to see? (Required)
performance/qps/transactions per seconds to be in the same order of magnitude as for non partitioned table, not 1/50 or less QPS.
3. What did you see instead (Required)
QPS of ~500 vs ~24k (of non partitioned table).
4. What is your TiDB version? (Required)
tidb_version(): Release Version: v8.3.0
Edition: Community
Git Commit Hash: 1a0c3ac
Git Branch: release-8.3
UTC Build Time: 2024-08-23 14:33:35
GoVersion: go1.22.1
Race Enabled: false
Check Table Before Drop: false
Store: tikv
The text was updated successfully, but these errors were encountered: