diff options
| author | Peter Eisentraut | 2020-06-09 08:41:41 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2020-06-09 08:41:41 +0000 |
| commit | 350f47786c3444d822d6d27829dd6a5426487150 (patch) | |
| tree | 747497cca046eaa83d16b77923b0e413018815b3 /src/backend | |
| parent | b1d32d3e3230f00b5baba08f75b4f665c7d6dac6 (diff) | |
Spelling adjustments
similar to 0fd2a79a637f9f96b9830524823df0454e962f96
Diffstat (limited to 'src/backend')
| -rw-r--r-- | src/backend/commands/explain.c | 4 | ||||
| -rw-r--r-- | src/backend/optimizer/plan/planner.c | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/commands/explain.c b/src/backend/commands/explain.c index efd7201d611..9092b4b3094 100644 --- a/src/backend/commands/explain.c +++ b/src/backend/commands/explain.c @@ -4238,7 +4238,7 @@ ExplainOpenGroup(const char *objtype, const char *labelname, /* * In YAML format, the grouping stack is an integer list. 0 means * we've emitted nothing at this grouping level AND this grouping - * level is unlabelled and must be marked with "- ". See + * level is unlabeled and must be marked with "- ". See * ExplainYAMLLineStarting(). */ ExplainYAMLLineStarting(es); @@ -4601,7 +4601,7 @@ ExplainJSONLineEnding(ExplainState *es) * * YAML lines are ordinarily indented by two spaces per indentation level. * The text emitted for each property begins just prior to the preceding - * line-break, except for the first property in an unlabelled group, for which + * line-break, except for the first property in an unlabeled group, for which * it begins immediately after the "- " that introduces the group. The first * property of the group appears on the same line as the opening "- ". */ 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 && |