| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, 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>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Subject: | Re: Add index scan progress to pg_stat_progress_vacuum |
| Date: | 2022-04-05 17:31:25 |
| Message-ID: | 20220405173125.lihxwb7ltpb4ywpu@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-04-05 16:42:28 +0000, Imseih (AWS), Sami wrote:
> > Why isn't the obvious thing to do here to provide a way to associate workers
> > with their leaders in shared memory, but to use the existing progress fields
> > to report progress? Then, when querying progress, the leader and workers
> > progress fields can be combined to show the overall progress?
>
> The original intent was this, however the workers
> can exit before the command completes and the
> worker progress data will be lost.
Can't the progress data trivially be inferred by the fact that the worker
completed?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2022-04-05 17:57:29 | Re: Mark all GUC variable as PGDLLIMPORT |
| Previous Message | Andres Freund | 2022-04-05 17:30:06 | Re: shared-memory based stats collector - v68 |