From: | Chris Cheston <ccheston(at)gmail(dot)com> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: postgres 7.4 at 100% |
Date: | 2004-06-29 08:37:30 |
Message-ID: | e071108e04062901377f6591c9@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
ok i just vacuumed it and it's taking slightly longer now to execute
(only about 8 ms longer, to around 701 ms).
Not using indexes for calllogs(from)... should I? The values for
calllogs(from) are not unique (sorry if I'm misunderstanding your
point).
Thanks,
Chris
On Tue, 29 Jun 2004 16:21:01 +0800, Christopher Kings-Lynne
<chriskl(at)familyhealth(dot)com(dot)au> wrote:
>
> > live=# explain analyze SELECT id FROM calllogs WHERE from = 'you';
> > QUERY PLAN
> > ----------------------------------------------------------------------------------------------------------
> > Seq Scan on calllogs (cost=0.00..136.11 rows=24 width=4) (actual
> > time=0.30..574.72 rows=143485 loops=1)
> > Filter: (from = 'you'::character varying)
> > Total runtime: 676.24 msec
> > (3 rows)
>
> Have you got an index on calllogs(from)?
>
> Have you vacuumed and analyzed that table recently?
>
> Chris
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2004-06-29 08:37:49 | Re: Query performance |
Previous Message | Christopher Kings-Lynne | 2004-06-29 08:21:01 | Re: postgres 7.4 at 100% |