Re: Add index scan progress to pg_stat_progress_vacuum - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Add index scan progress to pg_stat_progress_vacuum
Date
Msg-id 20220405173125.lihxwb7ltpb4ywpu@alap3.anarazel.de
Whole thread Raw
In response to Re: Add index scan progress to pg_stat_progress_vacuum  ("Imseih (AWS), Sami" <simseih@amazon.com>)
Responses Re: Add index scan progress to pg_stat_progress_vacuum  ("Imseih (AWS), Sami" <simseih@amazon.com>)
List 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?



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: shared-memory based stats collector - v68
Next
From: John Naylor
Date:
Subject: Re: Mark all GUC variable as PGDLLIMPORT