Re: Using the wrong index (very suboptimal), why? - Mailing list pgsql-general

From Shane Wright
Subject Re: Using the wrong index (very suboptimal), why?
Date
Msg-id 952015000A644E44B2FB8759E151093B01328287@exchange11.ad.edigitalresearch.com
Whole thread Raw
In response to Using the wrong index (very suboptimal), why?  ("Shane Wright" <shane.wright@edigitalresearch.com>)
List pgsql-general
Tom,

>>  Index Scan using index_answers_nidiid1 on answers
>> (cost=0.00..114.14 rows=1 width=60) (actual time=0.206..2398.645
>> rows=21891 loops=1)
>>    Index Cond: ((nid = 253869913) AND (iid1 = 535292129))
>>  Total runtime: 2424.769 ms
>Well, here's the problem all right: 1 row estimated vs 21891 actual.
>Is there something odd about the joint distribution of these two
>columns?

I should also clarify, there will almost always be many many rows that
match any nid/iid1 pair (for any nid or iid1 value that exists in this
table anyway).  The chance of there actually being only one result is
very small.  Most of the time this will be hundreds/thousands - but will
also be tens of thousands on a regular basis.  A hundred thousand or
more periodically.


Many thanks

Shane



pgsql-general by date:

Previous
From: "Shane Wright"
Date:
Subject: Re: Using the wrong index (very suboptimal), why?
Next
From: Herouth Maoz
Date:
Subject: Re: Copy/delete issue