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

Re: feature request: Loose index scans

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Gregg Lind <gregg(dot)lind(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: feature request: Loose index scans
Date: 2010-03-16 19:04:22
Message-ID: 12550.1268766262@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Mar 15, 2010 at 3:04 PM, Gregg Lind <gregg(dot)lind(at)gmail(dot)com> wrote:
>> As per http://osdir.com/ml/pgsql-hackers/2010-03/msg00331.html, I would
>> certainly find it helpful is count(distinct(myfield)) wasn't a full index
>> scan.

> We should maybe add this to our Todo file, if it's not there already
> (I don't see it on a quick look).

I think previous discussions of it have been under names like "skip
scan" (I certainly find "loose scan" to be completely useless
terminology, if indeed it even means what the OP wants at all).

However, most of the complaints about this were logged against PG
versions that wouldn't convert DISTINCT queries into hash aggregation.
COUNT(DISTINCT x) still doesn't.  Sometime it might be worth trying
to fix that.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Joshua TolleyDate: 2010-03-16 23:38:32
Subject: Re: Facing problem with pg_dump
Previous:From: Robert HaasDate: 2010-03-16 18:29:18
Subject: Re: feature request: Loose index scans

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