aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2017-06-17 19:03:12 -0400
committerPeter Eisentraut <peter_e@gmx.net>2017-06-17 19:03:12 -0400
commitf6da23f526cf622d2dbcee47695b4aedf8ab2c69 (patch)
tree5c0770d5c0a3910bdcd6f84f33baec0628407b82
parent806dccee23dfa3dd3b326354255cf0d5cb032f02 (diff)
downloadpostgresql-f6da23f526cf622d2dbcee47695b4aedf8ab2c69.tar.gz
postgresql-f6da23f526cf622d2dbcee47695b4aedf8ab2c69.zip
doc: Fix typo
Author: Julien Rouhaud <julien.rouhaud@dalibo.com>
-rw-r--r--doc/src/sgml/planstats.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/planstats.sgml b/doc/src/sgml/planstats.sgml
index 8caf297f859..838fcda6d21 100644
--- a/doc/src/sgml/planstats.sgml
+++ b/doc/src/sgml/planstats.sgml
@@ -501,8 +501,8 @@ EXPLAIN (ANALYZE, TIMING OFF) SELECT * FROM t WHERE a = 1;
of this clause to be 1%. By comparing this estimate and the actual
number of rows, we see that the estimate is very accurate
(in fact exact, as the table is very small). Changing the
- <literal>WHERE</> to use the <structfield>b</> column, an identical
- plan is generated. But observe what happens if we apply the same
+ <literal>WHERE</> condition to use the <structfield>b</> column, an
+ identical plan is generated. But observe what happens if we apply the same
condition on both columns, combining them with <literal>AND</>:
<programlisting>