"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>>> Assume the following:
>>> index on: (id, adate)
>>> constraint CHECK(adate > '01-01-2007' AND adate < '04-01-2007');
>>> The planner will not use the index listed above.
>> 
>> For what?

> select adate from parent where adate = '01-25-2007'

That's unsurprising.  Searching with only a lower-order index column
value seldom wins, 'cause you've got to scan the entire index.  The
constraint is irrelevant to this.

			regards, tom lane

In response to

• Re: Constraint exclusion oddity with composite index at 2007-06-01 21:03:07 from Joshua D. Drake

Responses

• Re: Constraint exclusion oddity with composite index at 2007-06-01 21:55:22 from Joshua D. Drake

pgsql-hackers by date

Next:	From: George Pavlov	Date: 2007-06-01 21:09:04
	Subject: Re: query log corrupted-looking entries
Previous:	From: Joshua D. Drake	Date: 2007-06-01 21:03:07
	Subject: Re: Constraint exclusion oddity with composite index