Inquiry About Determining Parallel Plans for REFRESH MATERIALIZED VIEW

public inbox for [email protected]  
help / color / mirror / Atom feed

From: Zhang Mingli <[email protected]>
To: PostgreSQL Hackers <[email protected]>
Subject: Inquiry About Determining Parallel Plans for REFRESH MATERIALIZED VIEW
Date: Thu, 16 Jan 2025 12:39:06 +0800
Message-ID: <f085f5d4-7858-48d0-b698-f0fd9e155c81@Spark> (raw)
In-Reply-To: <35481658-92e7-49c9-a3b5-77e8667ec971@Spark>
References: <35481658-92e7-49c9-a3b5-77e8667ec971@Spark>

Hi, all

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?

Zhang Mingli
www.hashdata.xyz

view thread (2+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Inquiry About Determining Parallel Plans for REFRESH MATERIALIZED VIEW
  In-Reply-To: <f085f5d4-7858-48d0-b698-f0fd9e155c81@Spark>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox