Re: [HACKERS] CTE inlining
От | Alvaro Herrera |
---|---|
Тема | Re: [HACKERS] CTE inlining |
Дата | |
Msg-id | 20170504173339.6zrrdrtklyr6d4ih@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: [HACKERS] CTE inlining (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] CTE inlining
Re: [HACKERS] CTE inlining Re: [HACKERS] CTE inlining |
Список | pgsql-hackers |
Andrew Dunstan wrote: > Hadn't though about LATERAL, good point. Still, there will be other cases. I'm not sure what your point is. We know that for some cases the optimization barrier semantics are useful, which is why the proposal is to add a keyword to install one explicitely: with materialized r as ( select json_populate_record(null::mytype, myjson) as x from mytable ) select (x).* from r; this would preserve the current semantics. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: