summaryrefslogtreecommitdiff
path: root/src/backend/optimizer/plan/planner.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2020-06-09 10:41:41 +0200
committerPeter Eisentraut <peter@eisentraut.org>2020-06-09 10:42:28 +0200
commita5202889b4c78e8ffcdd8be35d59f0a7aa644f64 (patch)
tree0d9670735e871e73a518dd09c8bb44720c22a624 /src/backend/optimizer/plan/planner.c
parent4d655f154565662cbd11f1ce5c0e6a90cd6a8f56 (diff)
Spelling adjustments
similar to 0fd2a79a637f9f96b9830524823df0454e962f96
Diffstat (limited to 'src/backend/optimizer/plan/planner.c')
-rw-r--r--src/backend/optimizer/plan/planner.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/optimizer/plan/planner.c b/src/backend/optimizer/plan/planner.c
index 357850624cc..5ac7fed6a4d 100644
--- a/src/backend/optimizer/plan/planner.c
+++ b/src/backend/optimizer/plan/planner.c
@@ -367,7 +367,7 @@ standard_planner(Query *parse, const char *query_string, int cursorOptions,
* parallel-restricted, and in either case it should be OK to impose
* parallel-mode restrictions. If that ends up breaking something, then
* either some function the user included in the query is incorrectly
- * labelled as parallel-safe or parallel-restricted when in reality it's
+ * labeled as parallel-safe or parallel-restricted when in reality it's
* parallel-unsafe, or else the query planner itself has a bug.
*/
glob->parallelModeNeeded = glob->parallelModeOK &&