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

From Robert Haas
Subject Re: [PATCH] explain tup_fetched/returned in monitoring-stats
Date
Msg-id CA+TgmoZDw8L7bZBjfd=dHQNzjAY-SfCvhHZWTg22qZsdozVpVQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] explain tup_fetched/returned in monitoring-stats  (Abhijit Menon-Sen <ams@2ndQuadrant.com>)
Responses Re: [PATCH] explain tup_fetched/returned in monitoring-stats  (Abhijit Menon-Sen <ams@2ndQuadrant.com>)
List pgsql-hackers
On Fri, Oct 12, 2012 at 2:05 PM, Abhijit Menon-Sen <ams@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Truncate if exists
Next
From: Heikki Linnakangas
Date:
Subject: Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown