Re: Slow query (planner insisting on using 'external merge' sort type)

From: Ian Pushee <ian(at)intuvisiontech(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Slow query (planner insisting on using 'external merge' sort type)
Date: 2015-06-19 14:53:43
Message-ID: 55842CF7.6080007@intuvisiontech.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Ian Pushee 2015-06-19 14:57:53 Re: Slow query (planner insisting on using 'external merge' sort type)
Previous Message Andreas Kretschmer 2015-06-19 14:47:09 Re: Slow query (planner insisting on using 'external merge' sort type)