Re: Slow query (planner insisting on using 'external merge' sort type) - Mailing list pgsql-performance

From Ian Pushee
Subject Re: Slow query (planner insisting on using 'external merge' sort type)
Date
Msg-id 55842CF7.6080007@intuvisiontech.com
Whole thread Raw
In response to Re: Slow query (planner insisting on using 'external merge' sort type)  (Igor Neyman <ineyman@perceptron.com>)
Responses Re: Slow query (planner insisting on using 'external merge' sort type)
List pgsql-performance

On 6/19/2015 10:46 AM, Igor Neyman wrote:
>
> Probably events_confidnce index is not very selective, that's why optimizer prefers seq scan.
> I'd try to create an index on (name, eventspy_id, camera_id, type, status).
>
> Also, the recent 9.2 is 9.2.13, you should upgrade.
>
> Regards,
> Igor Neyman

Hi Igor,

I already have an index for (name, eventspy_id, camera_id, type,
status)... that is the index being used (apparently silently) when I set
random_page_cost=1.0.

Thanks,
-Ian


pgsql-performance by date:

Previous
From: Andreas Kretschmer
Date:
Subject: Re: Slow query (planner insisting on using 'external merge' sort type)
Next
From: Ian Pushee
Date:
Subject: Re: Slow query (planner insisting on using 'external merge' sort type)