Skip to content

Fix wording to reflect poor performance of initial query before optimization #20534

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 27, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion explain-walkthrough.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ EXPLAIN ANALYZE SELECT count(*) FROM trips WHERE start_date BETWEEN '2017-07-01
5 rows in set (1.03 sec)
```

执行以上示例查询耗时 `1.03` 秒,说明执行性能较为理想
执行以上示例查询耗时 `1.03` 秒,说明执行性能不太理想

以上 `EXPLAIN ANALYZE` 的结果中,`actRows` 表明一些 `estRows` 预估数不准确(预估返回 10000 行数据但实际返回 19117643 行)。`└─TableFullScan_18` 算子的 `operator info` 列 (`stats:pseudo`) 信息也表明该算子的预估数不准确。

Expand Down