| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | "Hou, Zhijie" <houzj(dot)fnst(at)cn(dot)fujitsu(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Consider Parallelism While Planning For REFRESH MATERIALIZED VIEW |
| Date: | 2020-12-30 03:49:55 |
| Message-ID: | CALj2ACV-Ru+DNDvxVLv9tZhPqxEema4YUGymXkDYS9UpS8Zm7g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 30, 2020 at 8:03 AM Hou, Zhijie <houzj(dot)fnst(at)cn(dot)fujitsu(dot)com> wrote:
> > Yeah without explain analyze we can not show whether the parallelism is
> > picked in the test cases. What we could do is that we can add a plain RMV
> > test case in write_parallel.sql after CMV so that at least we can be ensured
> > that the parallelism will be picked because of the enforcement there. We
> > can always see the parallelism for the select part of explain analyze CMV
> > in write_parallel.sql and the same select query gets planned even in RMV
> > cases.
> >
> > IMO, the patch in this thread can go with test case addition to
> > write_parallel.sql. since it is very small.
> >
> > Thoughts?
>
> Yes, agreed.
Thanks. Added the test case. Attaching v2 patch. Please have a look.
With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Allow-parallel-mode-in-REFRESH-MAT-VIEW-planning.patch | application/x-patch | 2.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2020-12-30 03:55:33 | Re: Parallel Inserts in CREATE TABLE AS |
| Previous Message | Michael Paquier | 2020-12-30 03:46:12 | Re: Cleanup some -I$(libpq_srcdir) in makefiles |