Re: Consider Parallelism While Planning For REFRESH MATERIALIZED VIEW - Mailing list pgsql-hackers

From Luc Vlaming
Subject Re: Consider Parallelism While Planning For REFRESH MATERIALIZED VIEW
Date
Msg-id 3ccd914a-08a2-7d5e-06c1-cc6bc8143de8@swarm64.com
Whole thread Raw
In response to Re: Consider Parallelism While Planning For REFRESH MATERIALIZED VIEW  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
On 30-12-2020 04:49, Bharath Rupireddy wrote:
> On Wed, Dec 30, 2020 at 8:03 AM Hou, Zhijie <houzj.fnst@cn.fujitsu.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
> 

Hi,

Looks good to me and a nice simple improvement.

Passes everything according to http://cfbot.cputube.org/ so marked it 
therefore as ready for commiter.

Cheers,
Luc



pgsql-hackers by date:

Previous
From: Luc Vlaming
Date:
Subject: Re: New Table Access Methods for Multi and Single Inserts
Next
From: Luc Vlaming
Date:
Subject: Re: Consider Parallelism While Planning For REFRESH MATERIALIZED VIEW