1
0
mirror of https://github.com/postgres/postgres.git synced 2025-09-02 04:21:28 +03:00

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.
This commit is contained in:
Tom Lane
2016-12-23 11:53:35 -05:00
parent 3e6639a465
commit ff33d1456e
4 changed files with 12 additions and 12 deletions

View File

@@ -47,8 +47,8 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
child plan, which is the portion of the plan that will be executed in
parallel. If the <literal>Gather</> node is at the very top of the plan
tree, then the entire query will execute in parallel. If it is somewhere
else in the plan tree, then only that portion of the query will run in
parallel. In the example above, the query accesses only one table, so
else in the plan tree, then only the portion of the plan below it will run
in parallel. In the example above, the query accesses only one table, so
there is only one plan node other than the <literal>Gather</> node itself;
since that plan node is a child of the <literal>Gather</> node, it will
run in parallel.
@@ -76,8 +76,8 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
<para>
Every background worker process which is successfully started for a given
parallel query will execute the portion of the plan which is a descendent
of the <literal>Gather</> node. The leader will also execute that portion
parallel query will execute the portion of the plan below
the <literal>Gather</> node. The leader will also execute that portion
of the plan, but it has an additional responsibility: it must also read
all of the tuples generated by the workers. When the parallel portion of
the plan generates only a small number of tuples, the leader will often