Re: Consider Parallelism While Planning For REFRESH MATERIALIZED VIEW

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Consider Parallelism While Planning For REFRESH MATERIALIZED VIEW
Date: 2020-12-03 12:42:56
Message-ID: CALj2ACVvY0D_11GkJVm=KVnQ=R-DGn7NsM+6POp8o_MPpRSmaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 1, 2020 at 5:34 PM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
> Hi,
>
> I think we can pass CURSOR_OPT_PARALLEL_OK to pg_plan_query() for
> refresh mat view so that parallelism can be considered for the SELECT
> part of the previously created mat view. The refresh mat view queries
> can be faster in cases where SELECT is parallelized.
>
> Attaching a small patch. Thoughts?
>

Added this to commitfest, in case it is useful -
https://commitfest.postgresql.org/31/2856/

With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2020-12-03 12:56:34 Re: Additional improvements to extended statistics
Previous Message Amit Langote 2020-12-03 12:41:08 Re: Huge memory consumption on partitioned table with FKs