Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit ff33d14

Browse files
committed
Spellcheck: s/descendent/descendant/g
I got a little annoyed by reading documentation paragraphs containing both spellings within a few lines of each other. My dictionary says "descendant" is the preferred spelling, and it's certainly the majority usage in our tree, so standardize on that. For one usage in parallel.sgml, I thought it better to rewrite to avoid the term altogether.
1 parent 3e6639a commit ff33d14

File tree

4 files changed

+12
-12
lines changed

4 files changed

+12
-12
lines changed

doc/src/sgml/parallel.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -47,8 +47,8 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
4747
child plan, which is the portion of the plan that will be executed in
4848
parallel. If the <literal>Gather</> node is at the very top of the plan
4949
tree, then the entire query will execute in parallel. If it is somewhere
50-
else in the plan tree, then only that portion of the query will run in
51-
parallel. In the example above, the query accesses only one table, so
50+
else in the plan tree, then only the portion of the plan below it will run
51+
in parallel. In the example above, the query accesses only one table, so
5252
there is only one plan node other than the <literal>Gather</> node itself;
5353
since that plan node is a child of the <literal>Gather</> node, it will
5454
run in parallel.
@@ -76,8 +76,8 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
7676

7777
<para>
7878
Every background worker process which is successfully started for a given
79-
parallel query will execute the portion of the plan which is a descendent
80-
of the <literal>Gather</> node. The leader will also execute that portion
79+
parallel query will execute the portion of the plan below
80+
the <literal>Gather</> node. The leader will also execute that portion
8181
of the plan, but it has an additional responsibility: it must also read
8282
all of the tuples generated by the workers. When the parallel portion of
8383
the plan generates only a small number of tuples, the leader will often

doc/src/sgml/queries.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ FROM <replaceable>table_reference</replaceable> <optional>, <replaceable>table_r
146146
Instead of writing <literal>ONLY</> before the table name, you can write
147147
<literal>*</> after the table name to explicitly specify that descendant
148148
tables are included. There is no real reason to use this syntax any more,
149-
because searching descendent tables is now always the default behavior.
149+
because searching descendant tables is now always the default behavior.
150150
However, it is supported for compatibility with older releases.
151151
</para>
152152

doc/src/sgml/ref/alter_table.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1116,11 +1116,11 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable>
11161116
rename, or change the type of a column in the parent table without doing
11171117
same to the descendants. This ensures that the descendants always have
11181118
columns matching the parent. Similarly, a constraint cannot be renamed
1119-
in the parent without also renaming it in all descendents, so that
1120-
constraints also match between the parent and its descendents.
1121-
Also, because selecting from the parent also selects from its descendents,
1119+
in the parent without also renaming it in all descendants, so that
1120+
constraints also match between the parent and its descendants.
1121+
Also, because selecting from the parent also selects from its descendants,
11221122
a constraint on the parent cannot be marked valid unless it is also marked
1123-
valid for those descendents. In all of these cases, <command>ALTER TABLE
1123+
valid for those descendants. In all of these cases, <command>ALTER TABLE
11241124
ONLY</command> will be rejected.
11251125
</para>
11261126

src/backend/executor/execParallel.c

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -518,7 +518,7 @@ ExecInitParallelPlan(PlanState *planstate, EState *estate, int nworkers)
518518
}
519519

520520
/*
521-
* Copy instrumentation information about this node and its descendents from
521+
* Copy instrumentation information about this node and its descendants from
522522
* dynamic shared memory.
523523
*/
524524
static bool
@@ -666,7 +666,7 @@ ExecParallelGetQueryDesc(shm_toc *toc, DestReceiver *receiver,
666666
}
667667

668668
/*
669-
* Copy instrumentation information from this node and its descendents into
669+
* Copy instrumentation information from this node and its descendants into
670670
* dynamic shared memory, so that the parallel leader can retrieve it.
671671
*/
672672
static bool
@@ -706,7 +706,7 @@ ExecParallelReportInstrumentation(PlanState *planstate,
706706
}
707707

708708
/*
709-
* Initialize the PlanState and its descendents with the information
709+
* Initialize the PlanState and its descendants with the information
710710
* retrieved from shared memory. This has to be done once the PlanState
711711
* is allocated and initialized by executor; that is, after ExecutorStart().
712712
*/

0 commit comments

Comments
 (0)