I'm making some changes to a program that, among other things, reports
tup_fetched/tup_returned as if it were a cache hit rate, analogous to
blks_hit/blks_fetched.
The documentation didn't help me to understand if that was appropriate,
so I looked at the source and asked on IRC. It seems I'm not the first
person to be confused by these descriptions, so here's a tiny patch to
clarify the meaning of fetched and returned.
-- Abhijit
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 39ccfbb..ed42ce8 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -793,12 +793,12 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
<row>
<entry><structfield>tup_returned</></entry>
<entry><type>bigint</></entry>
- <entry>Number of rows returned by queries in this database</entry>
+ <entry>Number of rows returned by sequential scans in this database</entry>
</row>
<row>
<entry><structfield>tup_fetched</></entry>
<entry><type>bigint</></entry>
- <entry>Number of rows fetched by queries in this database</entry>
+ <entry>Number of rows fetched by index scans in this database</entry>
</row>
<row>
<entry><structfield>tup_inserted</></entry>
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
