From cf8e7b16a5f3e63fe692d042fefc0c9f09a23ebc Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 7 Mar 2016 21:48:17 -0500 Subject: [PATCH] Spell "parallel" correctly. Per David Rowley. --- src/backend/optimizer/README | 2 +- src/backend/optimizer/path/costsize.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/optimizer/README b/src/backend/optimizer/README index f9967c0828..7ecf8c8f0c 100644 --- a/src/backend/optimizer/README +++ b/src/backend/optimizer/README @@ -938,7 +938,7 @@ often very limited due to the difficulty of avoiding pipeline stalls. Consequently, we do not currently attempt to generate query plans that use this technique. -Instead, we focus on partitioning paralellism, which does not require +Instead, we focus on partitioning parallelism, which does not require that the underlying table be partitioned. It only requires that (1) there is some method of dividing the data from at least one of the base tables involved in the relation across multiple processes, (2) allowing diff --git a/src/backend/optimizer/path/costsize.c b/src/backend/optimizer/path/costsize.c index ffff3c0128..5350329998 100644 --- a/src/backend/optimizer/path/costsize.c +++ b/src/backend/optimizer/path/costsize.c @@ -238,7 +238,7 @@ cost_seqscan(Path *path, PlannerInfo *root, * only one worker, the leader often makes a very substantial * contribution to executing the parallel portion of the plan, but as * more workers are added, it does less and less, because it's busy - * reading tuples from the workers and doing whatever non-paralell + * reading tuples from the workers and doing whatever non-parallel * post-processing is needed. By the time we reach 4 workers, the * leader no longer makes a meaningful contribution. Thus, for now, * estimate that the leader spends 30% of its time servicing each -- 2.40.0