Re: Improving planning of outer joins
От | Tom Lane |
---|---|
Тема | Re: Improving planning of outer joins |
Дата | |
Msg-id | 13723.1134656742@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Improving planning of outer joins (Greg Stark <gsstark@mit.edu>) |
Ответы |
Re: Improving planning of outer joins
Re: Improving planning of outer joins |
Список | pgsql-hackers |
Greg Stark <gsstark@mit.edu> writes: > Tom Lane <tgl@sss.pgh.pa.us> writes: >> There is some stuff in the literature about how to make transformations >> of the last kind, but it requires additional executor smarts to do strange >> sorts of "generalized outer join" operations. > Would these "generalized outer join" operations be general enough to handle IN > semantics? Or other subqueries? No, AFAICT it's just a weird way of defining a join operation. I did find some papers that talked about ways to push joins up and down past aggregations and GROUP BY, but that's a problem for another day. regards, tom lane
В списке pgsql-hackers по дате отправления: