Re: Index not being used in MAX function (7.2.3) - Mailing list pgsql-general

From scott.marlowe
Subject Re: Index not being used in MAX function (7.2.3)
Date
Msg-id Pine.LNX.4.33.0306131414250.20410-100000@css120.ihs.com
Whole thread Raw
In response to Re: Index not being used in MAX function (7.2.3)  ("Jim C. Nasby" <jim@nasby.net>)
List pgsql-general
On Fri, 13 Jun 2003, Jim C. Nasby wrote:

> On Fri, Jun 13, 2003 at 10:37:46AM -0500, Bruno Wolff III wrote:
> > On Thu, Jun 12, 2003 at 17:26:11 -0500,
> >   "Jim C. Nasby" <jim@nasby.net> wrote:
> > > On Thu, Jun 12, 2003 at 12:08:15PM +0800, Ang Chin Han wrote:
> > >
> > > This becomes really important whenever pgsql gains the ability to use
> > > multiple indexes per table (someone smack me if it can do this now and I
> >
> > SMACK!
>
> You can use multiple indexes per query plan node? IE: if you have
> indexes on a and b, you can use both indexes when you do WHERE a=blah
> and b=foo? That's what I was reffering to...

In that instance you'd be better off with a multiple key index.




pgsql-general by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: Postgres performance comments from a MySQL user
Next
From: "Maksim Likharev"
Date:
Subject: Re: return records in DB load order??