pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gavin M. Roy <gmr@ehpg.net>
To: Chris Cheston <ccheston@gmail.com>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: postgres 7.4 at 100%
Date: Tue, 29 Jun 2004 09:03:24 -0700
Message-ID: <40E192CC.90707@ehpg.net> (raw)
In-Reply-To: <e071108e04062901377f6591c9@mail.gmail.com>
References: <e071108e04062423591d2b8aa9@mail.gmail.com>
	<1088397641.1105.10.camel@localhost>
	<17884.1088399982@sss.pgh.pa.us>
	<200406280947.59420.josh@agliodbs.com>
	<e071108e0406290100338c171d@mail.gmail.com>
	<40E1266D.3040607@familyhealth.com.au>
	<e071108e04062901377f6591c9@mail.gmail.com>

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)
>  
>




view thread (24+ messages)  latest in thread

Message-ID: <40E192CC.90707@ehpg.net>
Permalink:  ../40E192CC.90707@ehpg.net/
Also on:    postgresql.org/message-id/40E192CC.90707@ehpg.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: gmr@ehpg.net, ccheston@gmail.com, chriskl@familyhealth.com.au
  Subject: Re: postgres 7.4 at 100%
  In-Reply-To: <40E192CC.90707@ehpg.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox