Re: Add parallel columns for seq scan and index scan on pg_stat_all_tables and _indexes - Mailing list pgsql-hackers

On 07.10.2024 09:34, Guillaume Lelarge wrote:
> We need granularity because we have granularity in the config. There 
> is pg_stat_database because it gives the whole picture and it is 
> easier to monitor. And then, there is pg_stat_statements to analyze 
> problematic statements. And finally there is pg_stat_all* because you 
> can set parallel_workers on a specific table.
>
yes, I agree with you. Even when I experimented with vacuum settings for 
database and used my vacuum statistics patch [0] for analyzes , I first 
looked at this change in the number of blocks or deleted rows at the 
database level,
and only then did an analysis of each table and index.

[0] https://commitfest.postgresql.org/50/5012/

-- 
Regards,
Alena Rybakina
Postgres Professional