Re: Pulling up direct-correlated ANY_SUBLINK
От | Tom Lane |
---|---|
Тема | Re: Pulling up direct-correlated ANY_SUBLINK |
Дата | |
Msg-id | 27733.1568123328@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Pulling up direct-correlated ANY_SUBLINK (Richard Guo <riguo@pivotal.io>) |
Ответы |
Re: Pulling up direct-correlated ANY_SUBLINK
Re: Pulling up direct-correlated ANY_SUBLINK Re: Pulling up direct-correlated ANY_SUBLINK Re: Pulling up direct-correlated ANY_SUBLINK |
Список | pgsql-hackers |
Richard Guo <riguo@pivotal.io> writes: > Currently we do not try to pull up sub-select of type ANY_SUBLINK if it > refers to any Vars of the parent query, as indicated in the code snippet > below: > if (contain_vars_of_level((Node *) subselect, 1)) > return NULL; > Why do we have this check? Because the result would not be a join between two independent tables. > Can we try to pull up direct-correlated ANY SubLink with the help of > LATERAL? Perhaps. But what's the argument that you'd end up with a better plan? LATERAL pretty much constrains things to use a nestloop, so I'm not sure there's anything fundamentally different. regards, tom lane
В списке pgsql-hackers по дате отправления: