Re: postgres 7.4 at 100%

Поиск
Список
Период
Сортировка
От Chris Cheston
Тема Re: postgres 7.4 at 100%
Дата
Msg-id e071108e04062901377f6591c9@mail.gmail.com
обсуждение исходный текст
Ответ на Re: postgres 7.4 at 100%  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Ответы Re: postgres 7.4 at 100%  (Bruno Wolff III <bruno@wolff.to>)
Re: postgres 7.4 at 100%  ("Gavin M. Roy" <gmr@ehpg.net>)
Список 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@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
>
>

В списке pgsql-performance по дате отправления:

Предыдущее
От: Christopher Kings-Lynne
Дата:
Сообщение: Re: postgres 7.4 at 100%
Следующее
От: Richard Huxton
Дата:
Сообщение: Re: Query performance