From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | "Jason Tesser" <JTesser(at)nbbc(dot)edu>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: help with query speed |
Date: | 2004-02-12 20:50:48 |
Message-ID: | 200402122050.48083.dev@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thursday 12 February 2004 19:32, Jason Tesser wrote:
> Hi
>
> > Is there an index on:
> > testclass.classid
> I created the indexes and it speed up a little. Still a little slower
> than Access though. Which I think should not be. The testclass is a view
> not A query so I cannot make an index there.
But you can make one on the underlying table.
> What is the best way to index this stuff? Should I make one index
> (b-tree)
> And add all fkeys and pkey from that table?
You should apply indexes on columns where you need to discriminate amongst
different values quickly.
Anyway - what you need to do here is:
1. Run "VACUUM ANALYZE"
2. Run "EXPLAN ANALYZE SELECT tblroster.transcriptlink ..."
and post the output here.
Then we can see what query-plan PG is using.
3. Are you happy that your configuration is well tuned?
See http://www.varlena.com/varlena/GeneralBits/Tidbits/index.php
There is a performance tuning article and a breakdown of the config file
there.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Dann Corbit | 2004-02-12 20:51:17 | Re: help with query speed |
Previous Message | scott.marlowe | 2004-02-12 20:41:17 | Re: help with query speed |