Note that index-only scans can affect idx_tup_fetch.

An index-only scan that avoids heap fetches will increment idx_tup_read
but not idx_tup_fetch.

diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index a19e3f06ccc14eaeea69f7e349bc27fc0308f8ac..b9dc1d20013ae354f528b64bd8b225693865da64 100644 (file)
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -507,7 +507,8 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
     considering bitmap scans, because <structfield>idx_tup_read</> counts
     index entries retrieved from the index while <structfield>idx_tup_fetch</>
     counts live rows fetched from the table; the latter will be less if any
-    dead or not-yet-committed rows are fetched using the index.
+    dead or not-yet-committed rows are fetched using the index, or if any
+    heap fetches are avoided by means of an index-only scan.
    </para>
   </note>