| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Index not being used in MAX function (7.2.3) |
| Date: | 2003-06-13 20:15:03 |
| Message-ID: | Pine.LNX.4.33.0306131414250.20410-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)nasby(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2003-06-13 20:20:45 | Re: Pg_dumpall |
| Previous Message | Jim C. Nasby | 2003-06-13 20:12:39 | Re: Index not being used in MAX function (7.2.3) |