Re: Slow query fixed by replacing equality with a nested query

Поиск
Список
Период
Сортировка
От Michael Lewis
Тема Re: Slow query fixed by replacing equality with a nested query
Дата
Msg-id CAHOFxGoOz4RYH2Zj9C6EqcqLKKTwv=76onrOK0_DJGC8Fhu8vQ@mail.gmail.com
обсуждение исходный текст
Ответ на Slow query fixed by replacing equality with a nested query  (Valentin Janeiko <val.janeiko@gmail.com>)
Ответы RE: Slow query fixed by replacing equality with a nested query  (<val.janeiko@gmail.com>)
Список pgsql-performance
I don't see any reference to cte1. Is that expected?

I'm unclear why these sets are not just inner join'd on resource_surrogate_id. It seems like that column it is being selected as Sid1 in each CTE, and then the next one does the below. Why?

where resource_surrogate_id IN (SELECT Sid1 FROM cte_previous_number)

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

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: PostgreSQL and Linux CPU's
Следующее
От:
Дата:
Сообщение: RE: Slow query fixed by replacing equality with a nested query