From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
---|---|
To: | huaxin zhang <uwcssa(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: count(*) optimization |
Date: | 2005-09-06 19:44:13 |
Message-ID: | 36e6829205090612446b7dac6e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
huaxin... I'll save you the time... see the topic "MUCH ADO ABOUT COUNT(*)"
and "ADVANCED INDEX USAGE".
On 9/6/05, huaxin zhang <uwcssa(at)gmail(dot)com> wrote:
>
> not sure where to put this.
>
> I run two queries:
>
> 1. select count(*) from table where indexed_column<10;
> 2. select * from table where indexed_column<10;
>
> the indexed column is not clustered at all. I saw from the trace that
> both query runs
> through index scans on that index and takes the same amount of buffer
> hits and disk read. However, shouldn't the optimizer notice that the
> first query only needs to look at the indexes
> and possibly reduce the amount of buffer/disk visits?
>
> thanks
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2005-09-06 19:48:35 | Re: count(*) optimization |
Previous Message | huaxin zhang | 2005-09-06 19:21:16 | count(*) optimization |