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>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie>, 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-05-26 13:41:09
Message-ID: 93DB4449-2DE9-4DF5-94D2-E32D95854B0B@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> the function after updating the index status to
> PARALLEL_INDVAC_STATUS_COMPLETED.

> I also like this better. Will make the change.

I updated the patch. The progress function is called after
updating index status to PARALLEL_INDVAC_STATUS_COMPLETED.

I believe all comments have been addressed at this point.

Regards,

Sami Imseih
Amazon Web Services

Attachment Content-Type Size
v11-0001-Add-progress-reporting-callback-to-ParallelConte.patch application/octet-stream 2.6 KB
v11-0002-Show-progress-for-index-vacuums.patch application/octet-stream 9.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-05-26 14:36:47 Re: pg_upgrade test writes to source directory
Previous Message osumi.takamichi@fujitsu.com 2022-05-26 13:34:33 RE: Skipping schema changes in publication