From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 18 Nov 2007 18:42:03 +0000 (+0000)
Subject: Remove no-longer-accurate claim that REINDEX won't invalidate cached
X-Git-Url: http://waps.l3s.uni-hannover.de/gitweb/?a=commitdiff_plain;h=ee189c2454ae5edbcb8b385996892b0c66e0b89e;p=users%2Fbernd%2Fpostgres.git

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 badf61d2f3..f9a1dd38be 100644
--- 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>