| From: | Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add parallel columns for seq scan and index scan on pg_stat_all_tables and _indexes |
| Date: | 2024-10-08 15:24:54 |
| Message-ID: | d7822d57-1c5c-4f1f-a4a1-a04c517b74df@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-10-08 15:49:53 | Re: On disable_cost |
| Previous Message | Alena Rybakina | 2024-10-08 15:20:17 | Re: Add parallel columns for seq scan and index scan on pg_stat_all_tables and _indexes |