Re: How does the planner deal with multiple possible indexes?

From: "Gregory Maxwell" <gmaxwell(at)gmail(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: How does the planner deal with multiple possible indexes?
Date: 2006-07-19 22:29:51
Message-ID: e692861c0607191529p2753fac8g8daa366421a8ec8c@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/19/06, Jim C. Nasby <jnasby(at)pervasive(dot)com> wrote:
[snip]
> \d does list bdata__ident_filed_departure before bdata_ident; I'm
> wondering if the planner is finding the first index with ident_id in it
> and stopping there?

From my own experience it was grabbing the first that has the
requested field as its first member.. I haven't looked at the code to
see if that is the intended behavior.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ron Mayer 2006-07-19 22:31:14 Re: plPHP and plRuby
Previous Message Tom Lane 2006-07-19 22:23:44 Re: Max size of a btree index entry