Re: postgres 7.4 at 100%
От | Gavin M. Roy |
---|---|
Тема | Re: postgres 7.4 at 100% |
Дата | |
Msg-id | 40E192CC.90707@ehpg.net обсуждение исходный текст |
Ответ на | Re: postgres 7.4 at 100% (Chris Cheston <ccheston@gmail.com>) |
Ответы |
Re: postgres 7.4 at 100%
|
Список | 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 по дате отправления: