Postgres Pro
Downloads
Home   >   mailing lists

Re: How does the planner deal with multiple possible indexes? - Mailing list pgsql-hackers

From Gregory Maxwell
Subject Re: How does the planner deal with multiple possible indexes?
Date
Msg-id e692861c0607191529p2753fac8g8daa366421a8ec8c@mail.gmail.com
Whole thread Raw
In response to How does the planner deal with multiple possible indexes?  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: How does the planner deal with multiple possible indexes?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On 7/19/06, Jim C. Nasby <jnasby@pervasive.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.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Max size of a btree index entry
Next
From: Ron Mayer
Date:
Subject: Re: plPHP and plRuby