Re: [HACKERS] utility commands benefiting from parallel plan - Mailing list pgsql-hackers

From Haribabu Kommi
Subject Re: [HACKERS] utility commands benefiting from parallel plan
Date
Msg-id CAJrrPGdwojA1eFNDRsAdFJemM1XVNo7SvS8G1zd-kgVc3WZhQQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] utility commands benefiting from parallel plan  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] utility commands benefiting from parallel plan
List pgsql-hackers


On Sat, Feb 25, 2017 at 3:21 AM, Robert Haas <robertmhaas@gmail.com> wrote:
On Fri, Feb 24, 2017 at 11:43 AM, Haribabu Kommi
<kommi.haribabu@gmail.com> wrote:
> Here I attached an implementation patch that allows
> utility statements that have queries underneath such as
> CREATE TABLE AS, CREATE MATERIALIZED VIEW
> and REFRESH commands to benefit from parallel plan.
>
> These write operations not performed concurrently by the
> parallel workers, but the underlying query that is used by
> these operations are eligible for parallel plans.
>
> Currently the write operations are implemented for the
> tuple dest types DestIntoRel and DestTransientRel.
>
> Currently I am evaluating other write operations that can
> benefit with parallelism without side effects in enabling them.
>
> comments?

I think a lot more work than this will be needed.  See:

https://www.postgresql.org/message-id/CA+TgmoZC5ft_t9uQWSO5_1vU6H8oVyD=zyuLvRnJqTN==fvnhg@mail.gmail.com

...and the discussion which followed.


Thanks for the link.
Yes, it needs more work to support parallelism even for 
queries that involved in write operations like INSERT,
DELETE and UPDATE commands.

Regards,
Hari Babu
Fujitsu Australia

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] pg_upgrade loses security lables and COMMENTs on blobs
Next
From: Kyotaro HORIGUCHI
Date:
Subject: [HACKERS] Wrong variable type in KeepLogSeg