From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: COPY (query) TO ... doesn't allow parallelism |
Date: | 2017-06-01 04:28:42 |
Message-ID: | CAFiTN-ttnR9ZtnMmp34po7Aku9WY2yw_62HB4QFYZ7-EzOLztQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, May 31, 2017 at 7:19 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> At the moment $subject doesn't allow parallelism, because copy.c's
> pg_plan_query() invocation doesn't set the CURSOR_OPT_PARALLEL_OK
> flag.
>
> To me that appears to be an oversight rather than intentional. A
> somewhat annoying one at that, because it's not uncommong to use COPY to
> execute reports to a CSV file and such.
>
> Robert, am I missing a complication?
>
> I personally think we should fix this in 9.6 and 10, but I've to admit
> I'm not entirely impartial, because Citus hit this...
IMHO, For copy_to I don't see any problem in parallelizing it. I just
tested by changing the cursorOption and it's working in parallel.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
copy_to_parallel.patch | application/octet-stream | 465 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2017-06-01 04:41:35 | Re: Perfomance bug in v10 |
Previous Message | Andres Freund | 2017-06-01 04:06:13 | Re: walsender & parallelism |