| From: | Sami Imseih <samimseih(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| 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 03:16:23 |
| Message-ID: | CAN12+YKmLS5VvPO269A2op8hmkHJLzd2WKKZ4Fa1_PHT3HDBsw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
v8- looks good to me.
Only one doc nit:
+ During a parallel vacuum, the leader and each of its workers reports its
+ own row, all sharing the same <structfield>relid</structfield>. Only
+ <structfield>phase</structfield>,
I think we should make it more clear about how long the worker rows exist
for. Maybe the below:
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.
--
Sami
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Grigorev Jurij | 2026-10-01 03:18:11 | Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ |
| Previous Message | shihao zhong | 2026-10-01 02:56:03 | Commitfest PG20-2 is now closed |