Re: Very bad plan when using VIEW and IN (SELECT...*)

Поиск
Список
Период
Сортировка
Искать
От
Kevin Grittner
Тема
Re: Very bad plan when using VIEW and IN (SELECT...*)
Дата
Msg-id
4C65023F020000250003457D@gw.wicourts.gov
Ответ на
Список
Дерево обсуждения
Very bad plan when using VIEW and IN (SELECT...*) "Carlo Stonebanks" <stonec.register@sympatico.ca>
Re: Very bad plan when using VIEW and IN (SELECT...*) "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Very bad plan when using VIEW and IN (SELECT...*) "Carlo Stonebanks" <stonec.register@sympatico.ca>
"Carlo Stonebanks"  wrote:
 
> SELECT *
> FROM mdx_core.vw_provider AS p
> WHERE provider_id IN (SELECT 13083101)
> 
> I am using the simple IN (SELECT n) in QUERY 2 to simplify the
> problem. I noticed the oddity of the behaviour when I used a
> proper "IN (SELECT myId FROM myTable)"
 
Did you try?:
 
SELECT *
FROM mdx_core.vw_provider AS p
WHERE EXISTS (SELECT * FROM myTable WHERE myId = provider_id)
 
For any follow-up you should probably mention what version of
PostgreSQL this is and how it's configured.
 
http://wiki.postgresql.org/wiki/SlowQueryQuestions
 
-Kevin
В списке pgsql-performance по дате отправления
От: Michael March
Дата:
От: Carlo Stonebanks
Дата:
FAQ