sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-31 00:03:57 -04:00
Code Issues Projects Releases Wiki Activity

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

Browse Source 
plans.
This commit is contained in:
Tom Lane 2007-11-18 18:42:03 +00:00
parent b13602c6d0
commit 7129f26be0
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/ref/reindex.sgml
View File

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