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:18 +0300 |
commit | 31380bc7c204e7cfa9c9e1c62947909e2b38577c (patch) | |
tree | 20eebbeee3ce990061d46661a6d290e0221dfb20 /src | |
parent | 661dd23950f2e64646404605e99315d2379de0e5 (diff) | |
download | postgresql-31380bc7c204e7cfa9c9e1c62947909e2b38577c.tar.gz postgresql-31380bc7c204e7cfa9c9e1c62947909e2b38577c.zip |
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, |