diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2018-08-09 10:41:28 +0300 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2018-08-09 10:43:14 +0300 |
| commit | 83f2691a3f2bafa397ff1dcca94c4d059df0e056 (patch) | |
| tree | 609c4211601d910a041370d4fb0a8a682ac10aed /src | |
| parent | 87330e21c32793237791756ddffae676775e3aaa (diff) | |
Spell "partitionwise" consistently.
I'm not sure which spelling is better, "partitionwise" or "partition-wise",
but everywhere else we spell it "partitionwise", so be consistent.
Tatsuro Yamada reported the one in README, I found the other one with grep.
Discussion: https://www.postgresql.org/message-id/d25ebf36-5a6d-8b2c-1ff3-d6f022a56000@lab.ntt.co.jp
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/optimizer/README | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/optimizer/README b/src/backend/optimizer/README index 15af9ceff53..0db3d36208d 100644 --- a/src/backend/optimizer/README +++ b/src/backend/optimizer/README @@ -1106,8 +1106,8 @@ PartitionSchemeData object. This reduces memory consumed by PartitionSchemeData objects and makes it easy to compare the partition schemes of joining relations. -Partition-wise aggregates/grouping ----------------------------------- +Partitionwise aggregates/grouping +--------------------------------- If the GROUP BY clause has contains all of the partition keys, all the rows that belong to a given group must come from a single partition; therefore, |