From: | Ken Kato <katouknl(at)oss(dot)nttdata(dot)com> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Add last_vacuum_index_scans in pg_stat_all_tables |
Date: | 2022-07-04 09:29:08 |
Message-ID: | ce4a6ee93d78e2c4dafe4c1e515b342b@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi hackers,
I think having number of index scans of the last vacuum in
pg_stat_all_tables can be helpful. This value shows how efficiently
vacuums have performed and can be an indicator to increase
maintenance_work_mem.
It was proposed previously[1], but it was not accepted due to the
limitation of stats collector. Statistics are now stored in shared
memory, so we got more rooms to store statistics. I think this
statistics is still valuable for some people, so I am proposing this
again.
Best wishes,
--
Ken Kato
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
[1]
https://www.postgresql.org/message-id/20171010.192616.108347483.horiguchi.kyotaro%40lab.ntt.co.jp
Attachment | Content-Type | Size |
---|---|---|
show_index_scans_in_pg_stat_all_tables_v1.patch | text/x-diff | 7.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2022-07-04 09:32:38 | Re: Using PQexecQuery in pipeline mode produces unexpected Close messages |
Previous Message | Alvaro Herrera | 2022-07-04 09:27:53 | Re: Emit extra debug message when executing extension script. |