Re: Report index currently being vacuumed in pg_stat_progress_vacuum

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, shihao zhong <zhong950419(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com>
Subject: Re: Report index currently being vacuumed in pg_stat_progress_vacuum
Date: 2026-10-01 22:45:37
Message-ID: ar7ikaH9z8TWl2cd@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 01, 2026 at 01:23:50PM +0900, Michael Paquier wrote:
> On Wed, Sep 30, 2026 at 10:16:23PM -0500, Sami Imseih wrote:
>> During parallel index vacuuming or cleanup, the leader and each active
>> worker report separate rows, all sharing the same
>> <structfield>relid</structfield>. Worker rows exist only while the worker is
>> performing parallel vacuum work.
>
> Okay, your extra sentence works here.

I've slept over this suggestion, and it still felt a bit redundant
with the first sentence and the final one in the last paragraph added.

v8 applied. Thanks all for the discussion, nice addition to the
monitoring kit.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-10-01 22:57:38 Re: Use instr_time for pg_stat_database block read/write time counters
Previous Message Andres Freund 2026-10-01 22:39:21 Re: Partial indexes on system catalogs