Re: postgres 7.4 at 100% - Mailing list pgsql-performance

From Gavin M. Roy
Subject Re: postgres 7.4 at 100%
Date
Msg-id 40E192CC.90707@ehpg.net
Whole thread Raw
In response to Re: postgres 7.4 at 100%  (Chris Cheston <ccheston@gmail.com>)
Responses Re: postgres 7.4 at 100%  (Chris Cheston <ccheston@gmail.com>)
List 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@familyhealth.com.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@postgresql.org)
>
>


pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Slow INSERT
Next
From: Tom Lane
Date:
Subject: Re: Slow INSERT