Horton
Menu

Re: Add mode column to pg_stat_progress_vacuum

Sami Imseih <samimseih@gmail.com>

View thread
From: Sami Imseih <samimseih@gmail.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Nathan Bossart <nathandbossart@gmail.com>, Robert Treat <rob@xzilla.net>, Shinya Kato <shinya11.kato@gmail.com>, pgsql-hackers@postgresql.org
Date: 2025-10-07T19:40:02Z
Lists: pgsql-hackers 
> >  I wonder if we could be even more granular
> > for the "normal autovacuum" case and point to the reason the table was
> > chosen.  For example, was it the insert threshold, the update/delete
> > threshold, etc.?
>
> Sounds like reasonable information. I guess we might want to have such
> information in a cumulative statistics view but do you think it's
> better to have it in a dynamic statistics view?

+1 for this information in cumulative stats, on a per table level for sure.
I do think however the pg_stat_all_tables views is getting too wide
and moving new relation vacuum stats to a separate stats view will
be very useful.

--
Sami

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add started_by column to pg_stat_progress_analyze view.

  2. Add mode and started_by columns to pg_stat_progress_vacuum view.