Re: Inquiry About Determining Parallel Plans for REFRESH MATERIALIZED VIEW
| От | Zhang Mingli |
|---|---|
| Тема | Re: Inquiry About Determining Parallel Plans for REFRESH MATERIALIZED VIEW |
| Дата | |
| Msg-id | df288329-1e2e-4fc2-9b20-c91f3a195036@Spark обсуждение исходный текст |
| Ответ на | Re: Inquiry About Determining Parallel Plans for REFRESH MATERIALIZED VIEW (Yugo Nagata <nagata@sraoss.co.jp>) |
| Ответы |
Re: Inquiry About Determining Parallel Plans for REFRESH MATERIALIZED VIEW
|
| Список | pgsql-hackers |
Hi
www.hashdata.xyz
On Jan 16, 2025 at 14:04 +0800, Yugo Nagata <nagata@sraoss.co.jp>, wrote:
You will be able to log the plan during the REFRESH by using auto_explain and setting
log_analyze and log_nested_statements to on.
Hi Yugo,
Thank you for your help! That’s certainly a viable approach to logging the plan during the
REFRESH operation.However, I want to clarify that we’re particularly interested in examining the SQL cases. When there are numerous queries that may also include
REFRESH, it can be challenging to sift through the logs and identify the specific query we want to analyze using SQL.Ideally, it would be beneficial if we could obtain an explanation of the SQL associated with a
REFRESH command, allowing us to see the SELECT plan without having to execute the REFRESH itself. We could limit EXPLAIN utility command to only
REFRESH , on the AS SELECT part, similar to how we can with CREATE TABLE AS, is it possible and worthwhile?В списке pgsql-hackers по дате отправления: