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 17222.1181173665@sss.pgh.pa.us
Whole thread Raw
In response to Composite index planner issues Was: Re: Constraint exclusion oddity with composite index  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses 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:
>> I guess where I got confused is:
>> 
>> http://www.postgresql.org/docs/8.1/static/indexes-multicolumn.html
>> 
>> And explicitly:
>> 
>> A multicolumn B-tree index can be used with query conditions that 
>> involve any subset of the index's columns, but the index is most 
>> efficient when there are constraints on the leading (leftmost) columns.

> Considering the paragraph from the documentation above, should we change 
> the documentation?

That statement seems perfectly accurate to me.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Composite index planner issues Was: Re: Constraint exclusion oddity with composite index
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Composite index planner issues Was: Re: Constraint exclusion oddity with composite index