Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
[PATCH] explain tup_fetched/returned in monitoring-stats
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
Attachment: tup.diff
Description: text/x-diff (859 bytes)
Description: text/x-diff (859 bytes)
Responses
- Re: [PATCH] explain tup_fetched/returned in monitoring-stats at 2012-10-12 17:05:44 from Tom Lane
pgsql-hackers by date
Next: From: Amit Kapila Date: 2012-10-12 06:34:22 Subject: Re: Switching timeline over streaming replication Previous: From: Dean Rasheed Date: 2012-10-12 05:39:49 Subject: Re: Proof of concept: auto updatable views [Review of Patch]