Re: Performance Killer 'IN' ?

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Performance Killer 'IN' ?
Дата
Msg-id 8566.1143819939@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Performance Killer 'IN' ?  (Kai Hessing <kai.hessing@hobsons.de>)
Ответы Re: Performance Killer 'IN' ?  (Kai Hessing <kai.hessing@hobsons.de>)
Список pgsql-general
Kai Hessing <kai.hessing@hobsons.de> writes:
> Index Scan using phon_phon_idx on phon  (cost=0.00..5193.83 rows=530
> width=148) (actual time=0.146..0.146 rows=0 loops=1)
> ...
> Seq Scan on phon  (cost=0.00..1573304.58 rows=105931 width=148) (actual
> time=369563.565..369563.565 rows=0 loops=1)

You need to look into the discrepancy between estimated and actual row
counts.  (I suppose the reason you're showing 0 rows here is that you
already did these UPDATEs and so none of the rows in question pass the
status filter --- but how many rows are there matching the phon index
conditions?)  Perhaps a larger statistics target for the phon column
would be a good idea.

            regards, tom lane

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

Предыдущее
От: "Marko Kreen"
Дата:
Сообщение: Re: Performance Killer 'IN' ?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: How to use result column names in having cause