Re: Add index scan progress to pg_stat_progress_vacuum
От | Imseih (AWS), Sami |
---|---|
Тема | Re: Add index scan progress to pg_stat_progress_vacuum |
Дата | |
Msg-id | 399FC5A4-4DF8-4553-9E62-69322DDB63F5@amazon.com обсуждение исходный текст |
Ответ на | Re: Add index scan progress to pg_stat_progress_vacuum (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Add index scan progress to pg_stat_progress_vacuum
Re: Add index scan progress to pg_stat_progress_vacuum |
Список | 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
В списке pgsql-hackers по дате отправления: