Re: [PATCH] explain tup_fetched/returned in monitoring-stats

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] explain tup_fetched/returned in monitoring-stats
Date: 2012-10-15 14:28:17
Message-ID: CA+TgmoZDw8L7bZBjfd=dHQNzjAY-SfCvhHZWTg22qZsdozVpVQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 12, 2012 at 2:05 PM, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com> wrote:
> Yes. I'm sorry. Is there any concise description that applies? I think
> it's worth fixing, seeing that multiple competent people have got the
> wrong idea about what it means.

I don't think there is. I think we need to replace those counters
with something better. The status quo is quite bizarre.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2012-10-15 14:34:13 Re: Truncate if exists
Previous Message Heikki Linnakangas 2012-10-15 14:27:56 Re: BUG #7534: walreceiver takes long time to detect n/w breakdown