Query statistics lock is consuming excessive CPU resources during the auto-analysis check #49472
Labels
affects-7.5
This bug affects the 7.5.x(LTS) versions.
report/customer
Customers have encountered this bug.
severity/moderate
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Enhancement
If you have a large number of tables, the auto-analyze worker can help you analyze them efficiently by checking if they need to be analyzed. However, during the analysis, we need to obtain the stats lock information. If a table is already locked, then there is no need to analyze it.
If your table is small, it needs to be checked frequently which can lead to excessive CPU resource consumption due to the querying of statistics lock.
The text was updated successfully, but these errors were encountered: