Re: Subquery WHERE IN or WHERE EXISTS faster?

Поиск
Список
Период
Сортировка
От Gregory Stark
Тема Re: Subquery WHERE IN or WHERE EXISTS faster?
Дата
Msg-id 87k5g8phnq.fsf@oxford.xeocode.com
обсуждение исходный текст
Ответ на Re: Subquery WHERE IN or WHERE EXISTS faster?  (Ulrich <ulrich.mierendorff@gmx.net>)
Список pgsql-performance
"Ulrich" <ulrich.mierendorff@gmx.net> writes:

> Hi,
> Yes that looks strange. But it is not possible that I have processors in
> "users_processors" which do not appear in "processors", because
> "users_processors" contains foreign keys to "processors".
>
> If I remove the LIMIT 10 OFFSET 1 the line "Sort (cost=.... rows=11.."
> disappears and the query return 13 correct processors from "processors".

Oh, er, my bad. That makes perfect sense. The "actual" numbers can be affected
by what records are actually requested. The LIMIT prevents the records beyond
11 from ever being requested even though they exist.

While the bitmap heap scan has to fetch all the records even though they don't
all get used, the nested loop only fetches the records as requested.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's PostGIS support!

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

Предыдущее
От: Ulrich
Дата:
Сообщение: Re: Subquery WHERE IN or WHERE EXISTS faster?
Следующее
От: Greg Smith
Дата:
Сообщение: Re: A guide/tutorial to performance monitoring and tuning