| From: | Ragnar <gnari(at)hive(dot)is> |
|---|---|
| To: | "Silvela, Jaime (Exchange)" <JSilvela(at)Bear(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: speeding up big query lookup |
| Date: | 2006-08-26 09:52:47 |
| Message-ID: | 1156585967.26837.103.camel@localhost.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On fös, 2006-08-25 at 18:34 -0400, Silvela, Jaime (Exchange) wrote:
> This is a question on speeding up some type of queries.
>
> I have a very big table that catalogs measurements of some objects over
> time. Measurements can be of several (~10) types. It keeps the
> observation date in a field, and indicates the type of measurement in
> another field.
>
> I often need to get the latest measurement of type A for object X.
> The table is indexed by object_id.
one popular way is to create a composite index:
CREATE INDEX object_val_id_type_date
ON object_val(object_id,
object_val_type_id,
observation_date);
then you could
SELECT * FROM object_val
WHERE object_id=?
AND object_val_type_id=?
ORDER BY observation_date DESC
LIMIT 1;
Hope this helps
gnari
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jorge Godoy | 2006-08-26 10:42:19 | Re: alternative to using a sequence |
| Previous Message | Andrzej Folek | 2006-08-26 07:47:24 | mising chunk |