aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2017-06-02 19:05:57 -0700
committerAndres Freund <andres@anarazel.de>2017-06-02 19:11:15 -0700
commit34aebcf42a70089b76ff8e9ccda331f111153eeb (patch)
treef760f5fc95b20bfa623b7297810a7a759a22db46 /src
parentde492c17f064ea3ddcb73d9529f3e30a1483ffa5 (diff)
downloadpostgresql-34aebcf42a70089b76ff8e9ccda331f111153eeb.tar.gz
postgresql-34aebcf42a70089b76ff8e9ccda331f111153eeb.zip
Allow parallelism in COPY (query) TO ...;
Previously this was not allowed, as copy.c didn't set the CURSOR_OPT_PARALLEL_OK flag when planning the query. Set it. While the lack of parallel query for COPY isn't strictly speaking a bug, it does prevent parallelism from being used in a facility commonly used to run long running queries. Thus backpatch to 9.6. Author: Andres Freund Discussion: https://postgr.es/m/20170531231958.ihanapplorptykzm@alap3.anarazel.de Backpatch: 9.6, where parallelism was introduced.
Diffstat (limited to 'src')
-rw-r--r--src/backend/commands/copy.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/commands/copy.c b/src/backend/commands/copy.c
index 84b1a54cb9b..810bae5dadc 100644
--- a/src/backend/commands/copy.c
+++ b/src/backend/commands/copy.c
@@ -1527,7 +1527,7 @@ BeginCopy(ParseState *pstate,
}
/* plan the query */
- plan = pg_plan_query(query, 0, NULL);
+ plan = pg_plan_query(query, CURSOR_OPT_PARALLEL_OK, NULL);
/*
* With row level security and a user using "COPY relation TO", we