| From: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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-06 21:22:38 |
| Message-ID: | 399FC5A4-4DF8-4553-9E62-69322DDB63F5@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> At the beginning of a parallel operation, we allocate a chunk of>
> dynamic shared memory which persists even after some or all workers
> have exited. It's only torn down at the end of the parallel operation.
> That seems like the appropriate place to be storing any kind of data
> that needs to be propagated between parallel workers. The current
> patch uses the main shared memory segment, which seems unacceptable to
> me.
Correct, DSM does track shared data. However only participating
processes in the parallel vacuum can attach and lookup this data.
The purpose of the main shared memory is to allow a process that
Is querying the progress views to retrieve the information.
Regards,
Sami Imseih
Amazon Web Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2022-04-06 21:34:36 | Re: How about a psql backslash command to show GUCs? |
| Previous Message | Fabrízio de Royes Mello | 2022-04-06 21:12:08 | Re: trigger example for plsample |