Skip to content

Planner: Test TestCostModelVer2ScanRowSize tablescan row size is incorrect #57085

@terry1purcell

Description

@terry1purcell

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Running test TestCostModelVer2ScanRowSize - you can see that the table scan row size is (scan(1000*logrowsize(80)*tikv_scan_factor(40.7) - when it should be "scan(10000".

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

(scan(10000*logrowsize(80)*tikv_scan_factor(40.7) <--- 10,000

3. What did you see instead (Required)

(scan(1000*logrowsize(80)*tikv_scan_factor(40.7) <--- 1000

4. What is your TiDB version? (Required)

+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| tidb_version() |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Release Version: v8.5.0-alpha-31-g241c10294b
Edition: Community
Git Commit Hash: 241c102
Git Branch: fixscan
UTC Build Time: 2024-11-03 20:42:45
GoVersion: go1.23.0
Race Enabled: false
Check Table Before Drop: false
Store: unistore |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Metadata

Metadata

Assignees

Labels

affects-8.1This bug affects the 8.1.x(LTS) versions.report/customerCustomers have encountered this bug.severity/majorsig/plannerSIG: Plannertype/bugThe issue is confirmed as a bug.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions