aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTatsuo Ishii <ishii@postgresql.org>2016-10-14 07:45:25 +0900
committerTatsuo Ishii <ishii@postgresql.org>2016-10-14 07:45:25 +0900
commitb1ee762a6138df073d4b2b80c235dd9025a8532c (patch)
tree32b6213e9acfd4247f1c11fe10b55cbb62439a28
parent3cca13cbfcc5312f7ae1728213e197c6f37ca62a (diff)
downloadpostgresql-b1ee762a6138df073d4b2b80c235dd9025a8532c.tar.gz
postgresql-b1ee762a6138df073d4b2b80c235dd9025a8532c.zip
Fix typo.
Confirmed by Tom Lane.
-rw-r--r--doc/src/sgml/parallel.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/parallel.sgml b/doc/src/sgml/parallel.sgml
index 1e71529eeb3..94170b770bc 100644
--- a/doc/src/sgml/parallel.sgml
+++ b/doc/src/sgml/parallel.sgml
@@ -189,7 +189,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
Even when parallel query plan is generated for a particular query, there
are several circumstances under which it will be impossible to execute
that plan in parallel at execution time. If this occurs, the leader
- will execute the portion of the plan between below the <literal>Gather</>
+ will execute the portion of the plan below the <literal>Gather</>
node entirely by itself, almost as if the <literal>Gather</> node were
not present. This will happen if any of the following conditions are met:
</para>