Re: Composite index planner issues Was: Re: Constraint exclusion oddity with composite index

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Composite index planner issues Was: Re: Constraint exclusion oddity with composite index
Date: 2007-06-07 00:26:07
Message-ID: 17646.1181175967@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Joshua D. Drake" <jd(at)commandprompt(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2007-06-07 00:48:28 Re: [RFC] GSoC Work on readonly queries done so far
Previous Message Joshua D. Drake 2007-06-07 00:01:33 Re: Composite index planner issues Was: Re: Constraint exclusion oddity with composite index