Re: Sub-optimal plan chosen

From: bricklen <bricklen(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Sub-optimal plan chosen
Date: 2009-09-10 17:12:23
Message-ID: 33b743250909101012m4dbc2390wedfe8869f61a1488@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Sep 10, 2009 at 10:07 AM, bricklen <bricklen(at)gmail(dot)com> wrote:

> On Thu, Sep 10, 2009 at 10:02 AM, Robert Haas <robertmhaas(at)gmail(dot)com>wrote:
>
>> On Thu, Sep 10, 2009 at 12:56 PM, bricklen <bricklen(at)gmail(dot)com> wrote:
>> > On Thu, Sep 10, 2009 at 8:43 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> >>
>> >> bricklen <bricklen(at)gmail(dot)com> writes:
>> >> > Is there any other data I can provide to shed some light on this?
>> >>
>> >> The table and index definitions?
>> >>
>> >> The straight indexscan would probably win if the index column order
>> >> were ofid, date instead of date, ofid. I can't tell if you have
>> >> any other queries for which the existing column order is preferable,
>> >> though.
>> >>
>> >> regards, tom lane
>> >
>> >
>> > Changing the order of the WHERE predicates didn't help.
>>
>> He's talking about the index definition, not the WHERE clause. The
>> order of the WHERE clause is totally irrelevant.
>>
>>
> Ah, sorry, missed that.
>

I just created a new index as Tom said, and the query *does* use the new
index (where ofid precedes date in the definition).

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2009-09-10 17:56:07 Re: Sub-optimal plan chosen
Previous Message bricklen 2009-09-10 17:07:16 Re: Sub-optimal plan chosen