Re: seq-scan or index-scan

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: seq-scan or index-scan
Дата
Msg-id 8958.1341332035@sss.pgh.pa.us
обсуждение исходный текст
Ответ на seq-scan or index-scan  (Andreas Kretschmer <akretschmer@spamfence.net>)
Ответы Re: seq-scan or index-scan  (Andreas Kretschmer <akretschmer@spamfence.net>)
Список pgsql-general
Andreas Kretschmer <akretschmer@spamfence.net> writes:
> production=*# explain analyse select * from boxes;
>                                                   QUERY PLAN
> ---------------------------------------------------------------------------------------------------------------
>  Seq Scan on boxes  (cost=0.00..990783.99 rows=6499 width=581) (actual time=6.514..4588.136 rows=3060 loops=1)
>  Total runtime: 4588.729 ms
> (2 rows)

That cost estimate seems pretty dang large for a table with only 6500
rows.  I suspect this table is horribly bloated, and the indexscan
manages to win because it's not visiting pages that contain only dead
rows.  Try VACUUM FULL, and if that makes things saner, re-examine
your autovacuum settings.

            regards, tom lane

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

Предыдущее
От: "Tomas Vondra"
Дата:
Сообщение: Re: seq-scan or index-scan
Следующее
От: Benedict Holland
Дата:
Сообщение: function ave(integer) does not exist