Re: Add index scan progress to pg_stat_progress_vacuum

From: "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add index scan progress to pg_stat_progress_vacuum
Date: 2022-03-14 22:21:50
Message-ID: 4F14170D-AF67-4FDF-9EB0-2A1F8EA14899@amazon.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Attaching a v8 due to naming convention fixes and one slight change in where index_processed is set after all indexes are vacuumed.

s/indexes_completed/indexes_processed/

--
Sami Imseih
Amazon Web Services

Attachment Content-Type Size
v8-0001-Add-infrastructure-for-parallel-progress-reportin.patch application/octet-stream 9.9 KB
v8-0002-Show-progress-for-index-vacuums.patch application/octet-stream 10.8 KB
v8-0003-Expose-indexes-being-processed-in-a-VACUUM-operat.patch application/octet-stream 16.8 KB
v8-0004-Rename-index_vacuum_count-in-pg_stat_pogress_vacu.patch application/octet-stream 2.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Björn Harrtell 2022-03-14 22:23:47 Re: Logical replication timeout problem
Previous Message Robert Haas 2022-03-14 21:37:40 Re: standby recovery fails (tablespace related) (tentative patch and discussion)