On Tue, Jul 26, 2022 at 07:29:10PM -0400, Bruce Momjian wrote:
> > Summary paragraph:
> > "can only happen if" => "can only be created if"
>
> Yes, good point.
>
> Updated patch attached.
I applied this patch back to PG 11. (PG 10 had too many conflicts.) I
also added a mention about how indexes can prevent HOT to the index
introduction section; applied patch of that addition attached.
--
Bruce Momjian <br...@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml
index 023157d888..2a70e02f7c 100644
--- a/doc/src/sgml/indices.sgml
+++ b/doc/src/sgml/indices.sgml
@@ -103,7 +103,9 @@ CREATE INDEX test1_id_index ON test1 (id);
<para>
After an index is created, the system has to keep it synchronized with the
- table. This adds overhead to data manipulation operations.
+ table. This adds overhead to data manipulation operations. Indexes can
+ also prevent the creation of <link linkend="storage-hot">heap-only
+ tuples</link>.
Therefore indexes that are seldom or never used in queries
should be removed.
</para>
