From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Index not being used in MAX function (7.2.3) |
Date: | 2003-06-13 20:12:39 |
Message-ID: | 20030613201239.GV40542@flake.decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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...
--
Jim C. Nasby (aka Decibel!) jim(at)nasby(dot)net
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2003-06-13 20:15:03 | Re: Index not being used in MAX function (7.2.3) |
Previous Message | scott.marlowe | 2003-06-13 20:10:43 | Re: Postgres performance comments from a MySQL user |