Runtime error occurs when analyzing table #57448
Labels
affects-5.4
This bug affects 5.4.x versions.
affects-6.1
affects-6.5
affects-7.1
affects-7.5
affects-8.1
affects-8.5
impact/panic
severity/critical
sig/planner
SIG: Planner
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)
insert some values as follows:
test_data.csv
analyze table IDT_25727;
2. What did you expect to see? (Required)
analyse success
3. What did you see instead (Required)
ERROR 1105 (HY000): runtime error: slice bounds out of range [11:10]
[2024/11/18 03:16:55.452 +00:00] [ERROR] [analyze_col_v2.go:679] ["analyze worker panicked"] [recover="runtime error: slice bounds out of range [11:10]"] [stack="github.com/pingcap/tidb/pkg/executor.(*AnalyzeColumnsExecV2).subBuildWorker.func1\n\t/workspace/source/tidb/pkg/executor/analyze_col_v2.go:679\nruntime.gopanic\n\t/usr/local/go/src/runtime/panic.go:785\nruntime.goPanicSliceBU\n\t/usr/local/go/src/runtime/panic.go:161\ngithub.com/pingcap/tidb/pkg/statistics.BuildHistAndTopN\n\t/workspace/source/tidb/pkg/statistics/builder.go:461\ngithub.com/pingcap/tidb/pkg/executor.(*AnalyzeColumnsExecV2).subBuildWorker\n\t/workspace/source/tidb/pkg/executor/analyze_col_v2.go:818\ngithub.com/pingcap/tidb/pkg/executor.(*AnalyzeColumnsExecV2).buildSamplingStats.func6\n\t/workspace/source/tidb/pkg/executor/analyze_col_v2.go:363\ngithub.com/pingcap/tidb/pkg/executor.(*notifyErrorWaitGroupWrapper).Run.func1\n\t/workspace/source/tidb/pkg/executor/analyze_utils.go:172"]
[2024/11/18 03:16:55.452 +00:00] [ERROR] [analyze.go:455] ["receive error when saving analyze results"] [error="runtime error: slice bounds out of range [11:10]"]
4. What is your TiDB version? (Required)
Release Version: v8.5.0-alpha-134-g4a6bf46a5f
Edition: Community
Git Commit Hash: 4a6bf46
Git Branch: HEAD
UTC Build Time: 2024-11-16 07:53:03
GoVersion: go1.23.3
Race Enabled: false
Check Table Before Drop: false
Store: tikv
The text was updated successfully, but these errors were encountered: