From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | ow <oneway_111(at)yahoo(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: pg 7.4.rc1, Range query performance |
Date: | 2003-11-11 00:57:51 |
Message-ID: | 20031110165327.P34950@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Mon, 10 Nov 2003, ow wrote:
> --- Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> wrote:
> > I'm not sure that AK_abc is the best index for check a range on a and
> > single values on b and c. I'd think that something like an index
> > on (b,c,a) would probably be better for this purpose (without doing any
> > testing ;) ).
>
> That would not work for us since most of the time users are working with most
> recent data, hence column "a" is the first in the index.
Are you doing alot of queries where you're only searching on a? If so,
then you may want to consider a second, non-unique index to speed up this
sort of query. With a range query on a and fixed values on b and c, you're
really not utilizing an index in that order efficiently.
From | Date | Subject | |
---|---|---|---|
Next Message | Abdul Wahab Dahalan | 2003-11-11 01:06:27 | Query Problem |
Previous Message | Bruce Momjian | 2003-11-11 00:50:56 | Re: pg 7.4.rc1, Range query performance |