Re: postgres 7.4 at 100%

From: "Gavin M(dot) Roy" <gmr(at)ehpg(dot)net>
To: Chris Cheston <ccheston(at)gmail(dot)com>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-performance(at)postgresql(dot)org
Subject: Re: postgres 7.4 at 100%
Date: 2004-06-29 16:03:24
Message-ID: 40E192CC.90707@ehpg.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Is the from field nullable? If not, try "create index calllogs_from on
calllogs ( from );" and then do an explain analyze of your query.

Gavin

Chris Cheston wrote:

>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
>>
>>
>>
>>
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>
>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Marc 2004-06-29 16:17:36 Re: High load average with PostgreSQL 7.4.2 on debian/ibm eserver.
Previous Message Tom Lane 2004-06-29 16:02:57 Re: Slow INSERT