Re: Composite index planner issues Was: Re: Constraint exclusion oddity with composite index - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Composite index planner issues Was: Re: Constraint exclusion oddity with composite index
Date
Msg-id 17646.1181175967@sss.pgh.pa.us
Whole thread Raw
In response to Re: Composite index planner issues Was: Re: Constraint exclusion oddity with composite index  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
"Joshua D. Drake" <jd@commandprompt.com> writes:
> Tom Lane wrote:
>> That statement seems perfectly accurate to me.

> Considering an index of a,b if I search for b I would expect that the 
> planner could use the index.

It can.  Whether it will think that's a good idea is another question
entirely, and one that seems a bit beyond the scope of the discussion
you're mentioning.

Try forcing the issue with enable_seqscan, and see what sort of
estimated and actual costs you get ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Composite index planner issues Was: Re: Constraint exclusion oddity with composite index
Next
From: Jeff Davis
Date:
Subject: Re: [RFC] GSoC Work on readonly queries done so far