Remove no-longer-accurate claim that REINDEX won't invalidate cached

plans.

diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index badf61d2f3de5d082bb7550a4726085ed26cb325..f9a1dd38bef3be1ea8ce3828e8d6561313a84da3 100644 (file)
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -231,9 +231,7 @@ REINDEX { INDEX | TABLE | DATABASE | SYSTEM } <replaceable class="PARAMETER">nam
    subsequent <command>CREATE INDEX</> locks out writes but not reads; since
    the index is not there, no read will attempt to use it, meaning that there
    will be no blocking but reads might be forced into expensive sequential
-   scans.  Another important point is that the drop/create approach
-   invalidates any cached query plans that use the index, while
-   <command>REINDEX</> does not.
+   scans.
   </para>
 
   <para>