Re: Add last_vacuum_index_scans in pg_stat_all_tables
От | Ken Kato |
---|---|
Тема | Re: Add last_vacuum_index_scans in pg_stat_all_tables |
Дата | |
Msg-id | c4527bc8a1881cd904f7239af64d45a5@oss.nttdata.com обсуждение исходный текст |
Ответ на | Re: Add last_vacuum_index_scans in pg_stat_all_tables (Peter Geoghegan <pg@bowt.ie>) |
Ответы |
Re: Add last_vacuum_index_scans in pg_stat_all_tables
|
Список | pgsql-hackers |
On 2022-07-09 03:18, Peter Geoghegan wrote: > On Fri, Jul 8, 2022 at 10:47 AM Alvaro Herrera > <alvherre@alvh.no-ip.org> wrote: >> Saving some sort of history would be much more useful, but of course a >> lot more work. Thank you for the comments! Yes, having some sort of history would be ideal in this case. However, I am not sure how to implement those features at this moment, so I will take some time to consider. At the same time, I think having this metrics exposed in the pg_stat_all_tables comes in handy when tuning the maintenance_work_mem/autovacuume_work_mem even though it shows the value of only last vacuum/autovacuum. Regards, -- Ken Kato Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION
В списке pgsql-hackers по дате отправления: