RE: Consider Parallelism While Planning For REFRESH MATERIALIZED VIEW

From: "Hou, Zhijie" <houzj(dot)fnst(at)cn(dot)fujitsu(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(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 02:33:43
Message-ID: c1c4fd96d38a4c5b8b490d7b60f88c81@G08CNEXMBPEKD05.g08.fujitsu.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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.

Best regards,
houzj

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2020-12-30 02:42:44 lwlock optimization opportunities
Previous Message Andres Freund 2020-12-30 02:11:16 Re: [PATCH] LWLock self-deadlock detection