|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/ref/reindex.sgml,v 1.36 2007/01/31 23:26:04 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/ref/reindex.sgml,v 1.37 2007/11/18 18:42:03 tgl Exp $ |
3 | 3 | PostgreSQL documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -231,9 +231,7 @@ REINDEX { INDEX | TABLE | DATABASE | SYSTEM } <replaceable class="PARAMETER">nam |
231 | 231 | subsequent <command>CREATE INDEX</> locks out writes but not reads; since |
232 | 232 | the index is not there, no read will attempt to use it, meaning that there |
233 | 233 | will be no blocking but reads might be forced into expensive sequential |
234 | | - scans. Another important point is that the drop/create approach |
235 | | - invalidates any cached query plans that use the index, while |
236 | | - <command>REINDEX</> does not. |
| 234 | + scans. |
237 | 235 | </para> |
238 | 236 |
|
239 | 237 | <para> |
|