[PATCH] explain tup_fetched/returned in monitoring-stats - Mailing list pgsql-hackers

From Abhijit Menon-Sen
Subject [PATCH] explain tup_fetched/returned in monitoring-stats
Date
Msg-id 20121012060345.GA29214@toroid.org
Whole thread Raw
Responses Re: [PATCH] explain tup_fetched/returned in monitoring-stats  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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

pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: Proof of concept: auto updatable views [Review of Patch]
Next
From: Amit Kapila
Date:
Subject: Re: Switching timeline over streaming replication