Skip to content

Commit e2e1bbd

Browse files
committed
doc: clarify when expression indexes evaluate their expressions
Only non-HOT updates evaluate the index expression. Reported-by: Chris Lowder Discussion: https://postgr.es/m/163967385701.26064.15365003480975321072@wrigleys.postgresql.org Backpatch-through: 10
1 parent 4965f75 commit e2e1bbd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/src/sgml/indices.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -748,8 +748,8 @@ CREATE INDEX people_names ON people ((first_name || ' ' || last_name));
748748

749749
<para>
750750
Index expressions are relatively expensive to maintain, because the
751-
derived expression(s) must be computed for each row upon insertion
752-
and whenever it is updated. However, the index expressions are
751+
derived expression(s) must be computed for each row insertion
752+
and non-HOT update. However, the index expressions are
753753
<emphasis>not</emphasis> recomputed during an indexed search, since they are
754754
already stored in the index. In both examples above, the system
755755
sees the query as just <literal>WHERE indexedcolumn = 'constant'</literal>

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy