GitHub user jianlirong added a comment to the discussion: [Proposal] VACUUM statistics for performance analysis
I strongly support this proposal. Improving VACUUM statistics is a valuable step toward making Apache Cloudberry more observable and easier to operate in production. It aligns well with the broader goal of continuously improving the observability of the system, enabling DBAs to better understand maintenance costs, diagnose bottlenecks, and evaluate the effectiveness of autovacuum tuning. As we move forward, I think a few aspects deserve particular attention: - **Statistics accuracy and semantics:** Clearly define what each metric represents, especially the distinction between cumulative work and current state. - **MPP-level visibility:** Preserve per-segment statistics alongside cluster-wide aggregates, so that local bottlenecks are not hidden by global averages. - **Production overhead and reliability:** Carefully evaluate the overhead of collecting statistics and ensure correct behavior across resets, restarts, and segment failures. - **Historical analysis:** Consider integration with tools such as pg_profile to make it easier to track trends and compare maintenance performance over time. Overall, this is a meaningful improvement, and I look forward to seeing it evolve into a practical part of Cloudberry's operational observability toolkit. Thanks for the great work! Lirong GitHub link: https://github.com/apache/cloudberry/discussions/2118#discussioncomment-19010545 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
