Re: [HACKERS] COPY (query) TO ... doesn't allow parallelism - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] COPY (query) TO ... doesn't allow parallelism
Date
Msg-id 20170601160428.ipmzwvowgi3fexpo@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] COPY (query) TO ... doesn't allow parallelism  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [HACKERS] COPY (query) TO ... doesn't allow parallelism  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On 2017-06-01 21:23:04 +0530, Amit Kapila wrote:
> On a related note, I think it might be better to have an
> IsInParallelMode() check in this case as we have at other places.
> This is to ensure that if this command is invoked via plpgsql function
> and that function runs is the parallel mode, it will act as a
> safeguard.

Hm? Which other places do it that way?  Isn't standard_planner()
centralizing such a check?

- Andres



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] COPY (query) TO ... doesn't allow parallelism
Next
From: Amit Kapila
Date:
Subject: Re: [HACKERS] COPY (query) TO ... doesn't allow parallelism