[PATCH] explain tup_fetched/returned in monitoring-stats

From: Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: [PATCH] explain tup_fetched/returned in monitoring-stats
Date: 2012-10-12 06:03:45
Message-ID: 20121012060345.GA29214@toroid.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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

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 Content-Type Size
tup.diff text/x-diff 859 bytes


Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2012-10-12 06:34:22 Re: Switching timeline over streaming replication
Previous Message Dean Rasheed 2012-10-12 05:39:49 Re: Proof of concept: auto updatable views [Review of Patch]