Re: sub-select in IN clause results in sequential scan

Поиск
Список
Период
Сортировка
Искать
От
Robert Haas
Тема
Re: sub-select in IN clause results in sequential scan
Дата
Msg-id
603c8f070910290835h10930c9dkb3e4677aeacd715b@mail.gmail.com
Ответ на
Re: sub-select in IN clause results in sequential scan (Anj Adu)
Список
Дерево обсуждения
sub-select in IN clause results in sequential scan Anj Adu <fotographs@gmail.com>
Re: sub-select in IN clause results in sequential scan Grzegorz Jaśkiewicz <gryzman@gmail.com>
Re: sub-select in IN clause results in sequential scan Angayarkanni <kangayarkanni@gmail.com>
Re: sub-select in IN clause results in sequential scan Anj Adu <fotographs@gmail.com>
Re: sub-select in IN clause results in sequential scan Robert Haas <robertmhaas@gmail.com>
Re: sub-select in IN clause results in sequential scan Anj Adu <fotographs@gmail.com>
Re: sub-select in IN clause results in sequential scan Grzegorz Jaśkiewicz <gryzman@gmail.com>
Re: sub-select in IN clause results in sequential scan Robert Haas <robertmhaas@gmail.com>
Re: sub-select in IN clause results in sequential scan Bob Lunney <bob_lunney@yahoo.com> 
On Thu, Oct 29, 2009 at 10:10 AM, Anj Adu  wrote:
> Join did not help. A sequential scan is still being done. The
> hardcoded value in the IN clause performs the best. The time
> difference is more than an order of magnitude.

If you want help debugging a performance problem, you need to post
your EXPLAIN ANALYZE results.

http://wiki.postgresql.org/wiki/Guide_to_reporting_problems

...Robert
В списке pgsql-performance по дате отправления
Предыдущее
От: Ludwik Dylag
Дата:
Следующее
От: Anj Adu
Дата:
FAQ