Re: Vacuum timing in pg_stat_all_tables - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Vacuum timing in pg_stat_all_tables
Date
Msg-id aBKnEf_yrcTcjIj7@paquier.xyz
Whole thread Raw
In response to Re: Vacuum timing in pg_stat_all_tables  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
List pgsql-hackers
On Wed, Mar 12, 2025 at 10:52:57AM +0000, Bertrand Drouvot wrote:
> Note that it does not add extra explanation to "cost-based delay". If we feel the
> need we could add a link to "<xref linkend="runtime-config-resource-vacuum-cost"/>"
> like it has been done for delay_time in bb8dff9995f.

Sorry for the delay, this has been sitting in my inbox for some time,
and I am catching with some of my backlog.

       <para>
-       Total time this table has been manually vacuumed, in milliseconds
+       Total time this table has been manually vacuumed, in milliseconds. (This
+       includes the time spent sleeping due to cost-based delay.)
       </para></entry>

Hmm, okay, adding this information to these four new fields is fine
here, so I'll apply that on HEAD shortly.  I can see that this matches
with the style used for some of the other fields, like n_tup_upd for the
details regarding HOT.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Batch TIDs lookup in ambulkdelete
Next
From: Michael Paquier
Date:
Subject: Re: Prevent an error on attaching/creating a DSM/DSA from an interrupt handler.