Inquiry About Determining Parallel Plans for REFRESH MATERIALIZED VIEW
| От | Zhang Mingli |
|---|---|
| Тема | Inquiry About Determining Parallel Plans for REFRESH MATERIALIZED VIEW |
| Дата | |
| Msg-id | f085f5d4-7858-48d0-b698-f0fd9e155c81@Spark обсуждение исходный текст |
| Ответы |
Re: Inquiry About Determining Parallel Plans for REFRESH MATERIALIZED VIEW
|
| Список | pgsql-hackers |
Hi, all
I am currently exploring the execution of the
During development, we want to ascertain whether the
Currently, we have configured the necessary settings for parallel queries and have been recording the execution time of the
However, I’m looking for a more definitive way to verify if the plan is indeed parallel during the execution of the
Any suggestions?
I am currently exploring the execution of the
REFRESH MATERIALIZED VIEW command and have a specific question regarding the underlying query plan. As you know, the REFRESH command is a utility command, and using EXPLAIN REFRESH does not provide a plan structure for analysis.During development, we want to ascertain whether the
SELECT part of the REFRESH command executes with a parallel plan. While I understand that we can run EXPLAIN on the SELECT statement directly, we are interested in knowing if there is a method to determine the execution plan under the REFRESH command context.Currently, we have configured the necessary settings for parallel queries and have been recording the execution time of the
REFRESH command to compare parallel and non-parallel executions. However, I’m looking for a more definitive way to verify if the plan is indeed parallel during the execution of the
REFRESH command.Any suggestions?
www.hashdata.xyz
В списке pgsql-hackers по дате отправления: