8000 Spell "partitionwise" consistently. · postgrespro/postgres_cluster@83f2691 · GitHub
[go: up one dir, main page]
Skip to content

Commit 83f2691

Browse files
hlinnakahlinnaka
committed
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
1 parent 87330e2 commit 83f2691

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

‎contrib/postgres_fdw/expected/postgres_fdw.out‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8316,7 +8316,7 @@ SELECT t1.a,t1.b FROM fprt1 t1, LATERAL (SELECT t2.a, t2.b FROM fprt2 t2 WHERE t
83168316
400 | 400
83178317
(4 rows)
83188318

8319-
-- with PHVs, partition-wise join selected but no join pushdown
8319+
-- with PHVs, partitionwise join selected but no join pushdown
83208320
EXPLAIN (COSTS OFF)
83218321
SELECT t1.a, t1.phv, t2.b, t2.phv FROM (SELECT 't1_phv' phv, * FROM fprt1 WHERE a % 25 = 0) t1 FULL JOIN (SELECT 't2_phv' phv, * FROM fprt2 WHERE b % 25 = 0) t2 ON (t1.a = t2.b) ORDER BY t1.a, t2.b;
83228322
QUERY PLAN

‎contrib/postgres_fdw/sql/postgres_fdw.sql‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2244,7 +2244,7 @@ EXPLAIN (COSTS OFF)
22442244
SELECT t1.a,t1.b FROM fprt1 t1, LATERAL (SELECT t2.a, t2.b FROM fprt2 t2 WHERE t1.a = t2.b AND t1.b = t2.a) q WHERE t1.a%25 = 0 ORDER BY 1,2;
22452245
SELECT t1.a,t1.b FROM fprt1 t1, LATERAL (SELECT t2.a, t2.b FROM fprt2 t2 WHERE t1.a = t2.b AND t1.b = t2.a) q WHERE t1.a%25 = 0 ORDER BY 1,2;
22462246

2247-
-- with PHVs, partition-wise join selected but no join pushdown
2247+
-- with PHVs, partitionwise join selected but no join pushdown
22482248
EXPLAIN (COSTS OFF)
22492249
SELECT t1.a, t1.phv, t2.b, t2.phv FROM (SELECT 't1_phv' phv, * FROM fprt1 WHERE a % 25 = 0) t1 FULL JOIN (SELECT 't2_phv' phv, * FROM fprt2 WHERE b % 25 = 0) t2 ON (t1.a = t2.b) ORDER BY t1.a, t2.b;
22502250
SELECT t1.a, t1.phv, t2.b, t2.phv FROM (SELECT 't1_phv' phv, * FROM fprt1 WHERE a % 25 = 0) t1 FULL JOIN (SELECT 't2_phv' phv, * FROM fprt2 WHERE b % 25 = 0) t2 ON (t1.a = t2.b) ORDER BY t1.a, t2.b;

‎src/backend/optimizer/README‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1106,8 +1106,8 @@ PartitionSchemeData object. This reduces memory consumed by
11061106
PartitionSchemeData objects and makes it easy to compare the partition schemes
11071107
of joining relations.
11081108

1109-
Partition-wise aggregates/grouping
1110-
----------------------------------
1109+
Partitionwise aggregates/grouping
1110+
---------------------------------
11111111

11121112
If the GROUP BY clause has contains all of the partition keys, all the rows
11131113
that belong to a given group must come from a single partition; therefore,

0 commit comments

Comments
 (0)
0