Re: [HACKERS] Use of Indicies ... - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Use of Indicies ...
Date
Msg-id 14946.948693518@sss.pgh.pa.us
Whole thread Raw
In response to Use of Indicies ...  (The Hermit Hacker <scrappy@hub.org>)
Responses Re: [HACKERS] Use of Indicies ...
List pgsql-hackers
The Hermit Hacker <scrappy@hub.org> writes:
> There is an index on all three conditions in the WHERE clause:
> Yet EXPLAIN shows:
> Aggregate  (cost=2.05 rows=1 width=4)
-> Index Scan using referrer_link_counter_id on referrer_link  (cost=2.05 rows=1 width=4)

> Why does EXPLAIN only show the use of one of the indices, why counter_id
> and why not all three?

Indexscans only know how to use one index at a time.

The optimizer picked the counter_id index out of the three available
choices because it thought that would be the cheapest (most selective)
alternative --- or, if the computed selectivities were all the same,
just because it happened to try that one first.

Do you have reason to think that one of the other indexes would have
been cheaper?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Happy column dropping
Next
From: Chris Bitmead
Date:
Subject: Re: ORDBMS<->OID (Re: [HACKERS] Happy column dropping)