Re: Add last_vacuum_index_scans in pg_stat_all_tables

From: Ken Kato <katouknl(at)oss(dot)nttdata(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add last_vacuum_index_scans in pg_stat_all_tables
Date: 2022-07-15 08:49:44
Message-ID: c4527bc8a1881cd904f7239af64d45a5@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022-07-09 03:18, Peter Geoghegan wrote:
> On Fri, Jul 8, 2022 at 10:47 AM Alvaro Herrera
> <alvherre(at)alvh(dot)no-ip(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2022-07-15 09:00:13 Re: Problem about postponing gathering partial paths for topmost scan/join rel
Previous Message Wenjing Zeng 2022-07-15 08:37:16 Re: [Commitfest 2022-07] Begins Now