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 04:23:50
Message-ID: ar3gVvZVpTyob5E8@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2026-10-01 04:42:00 Re: WAL segment file descriptor leak on read errors can PANIC the server
Previous Message Bharath Rupireddy 2026-10-01 04:18:11 Re: Parallel vacuum: I/O timings in the log leave out the parallel workers