The estimation error is large. Consider checking the health of the statistics

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 估算误差较大。可以考虑检查统计信息的健康度

| username: 大钢镚13146

In the slow SQL analysis on the dashboard, it shows a table with a significant estimation error. It suggests checking the health of the statistics. However, I see that the row count of the statistics on the backend is accurate, and I have manually executed ANALYZE TABLE. Could it be that this type of statistics collection does not gather index information, or is the dashboard displaying incorrectly?

| username: 大钢镚13146 | Original post link

Actual Rows: 98

Estimate Rows: 19442

| username: cassblanca | Original post link

show analyze status where Table_schema=‘******’; – During the process of collecting statistics, you can query the execution status using the show analyze status statement.
SELECT * FROM information_schema.tidb_statistics_meta; – Query the timestamp of the statistics.