Re: Vacuum timing in pg_stat_all_tables
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Cc: Nathan Bossart <nathandbossart@gmail.com>, Magnus Hagander <magnus@hagander.net>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>, "Imseih (AWS), Sami" <simseih@amazon.com>
Date: 2025-04-30T22:41:21Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
doc: Mention cost-based delays for total_[auto]{vacuum,analyze}_time
- 92ee8a4df5b5 18.0 landed
-
Add cost-based vacuum delay time to progress views.
- bb8dff9995f2 18.0 cited
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