postgres.git / summary / log / commit / refs

commit    f6da23f526cf622d2dbcee47695b4aedf8ab2c69
Author:   Peter Eisentraut <peter_e@gmx.net>
Date:     Sat Jun 17 23:03:12 2017 +0000
First released in: 10.0

    doc: Fix typo
    
    Author: Julien Rouhaud <julien.rouhaud@dalibo.com>


 doc/src/sgml/planstats.sgml | 4 ++--
 1 file 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>


[parent: 806dccee23df]