Skip site navigation (1) Skip section navigation (2)

Re: show Heap Fetches in EXPLAIN for index-only scans

From: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: show Heap Fetches in EXPLAIN for index-only scans
Date: 2012-01-13 15:41:45
Message-ID: CAEYLb_VgER4ED9SNOJDHvtYZwU6EsO-mXV6xrx4fss6XN4MnbA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 13 January 2012 15:31, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Jan 13, 2012 at 10:29 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> Would also be good to have counter sin pg_stat_* for this, since you'd
>> usually want to look at this kind of data over time as well. In your
>> plans? ;)
>
> Not really.  I don't have a clear enough idea about what that should
> look like, and I expect a vigorous debate over the distributed cost of
> another counter.  But I'm happy to have someone who feels more
> strongly about it than I do take up the cause.

Maybe the the ioss_HeapFetches field should be a uint32? That's all
it's going to be on some platforms anyway.

-- 
Peter Geoghegan       http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-01-13 15:43:37
Subject: Re: Text comparison suddenly can't find collation?
Previous:From: Robert HaasDate: 2012-01-13 15:36:32
Subject: Re: Disabled features on Hot Standby

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group