mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-01-24 18:55:04 +08:00
docs: mention that expression indexes need analyze
Expression indexes can't benefit from pre-computed statistics on columns. Reported-by: Nikolay Samokhvalov Discussion: https://postgr.es/m/CANNMO++5rw9RDA=p40iMVbMNPaW6O=S0AFzTU=KpYHRpCd1voA@mail.gmail.com Author: Nikolay Samokhvalov, modified Backpatch-through: 9.5
This commit is contained in:
parent
66a8f09048
commit
3370207986
@ -745,6 +745,16 @@ Indexes:
|
||||
sort high</quote>, in queries that depend on indexes to avoid sorting steps.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The regularly system collects statistics on all of a table's
|
||||
columns. Newly-created non-expression indexes can immediately
|
||||
use these statistics to determine an index's usefulness.
|
||||
For new expression indexes, it is necessary to run <link
|
||||
linkend="sql-analyze"><command>ANALYZE</command></link> or wait for
|
||||
the <link linkend="autovacuum">autovacuum daemon</link> to analyze
|
||||
the table to generate statistics about new expression indexes.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
For most index methods, the speed of creating an index is
|
||||
dependent on the setting of <xref linkend="guc-maintenance-work-mem"/>.
|
||||
|
Loading…
Reference in New Issue
Block a user