Re: Report index currently being vacuumed in pg_stat_progress_vacuum

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Sami Imseih <samimseih(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-09-18 01:00:08
Message-ID: CAGRkXqRdus_6EfVeeuvNtSWEo1Gf5E3T3RmDsL14Ami=3CC4OA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Michael,

> 0003 and 0004 are not things I can get much into, echoing with the
> recent following message:
> https://www.postgresql.org/message-id/aqqmGGS6qqm5LI0Z%40alvherre.pgsql

Thanks for the pointer. I had not seen that thread, withdraw 0003 and 0004.

I will work with Manu and Alvaro on the progress reporting test
framework in that thread. This patch would make a good first user.

Thanks,
Shihao

Attachment Content-Type Size
v7-0002-Remove-IndexVacuumInfo.report_progress.patch application/octet-stream 4.7 KB
v7-0001-Report-per-index-vacuum-progress-in-pg_stat_progr.patch application/octet-stream 17.8 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shihao zhong 2026-09-18 01:02:06 Re: pg_plan_advice: add NO_ scan and join method tags
Previous Message shihao zhong 2026-09-18 00:52:39 Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout