Re: Inlining functions with "expensive" parameters
От | Robert Haas |
---|---|
Тема | Re: Inlining functions with "expensive" parameters |
Дата | |
Msg-id | CA+TgmoZd+X-A0ZgGd9zzzC_tYcqPsY7uS=DER3ox0f+hFZpq3w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Inlining functions with "expensive" parameters (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: Inlining functions with "expensive" parameters
Re: Inlining functions with "expensive" parameters Re: Inlining functions with "expensive" parameters |
Список | pgsql-hackers |
On Thu, Nov 16, 2017 at 2:51 PM, Andres Freund <andres@anarazel.de> wrote: > Right, but it doesn't sound that hard to introduce. Basically there'd need to be a WithParamValue node, that first evaluatesparameters and then executes the child expression. I'm thinking of doing this hierarchically so there's less issueswith the setting of the param value being moved away from the child expression using it. I don't quite follow the need for this. I mean, if we just stick a Param reference in there and create a corresponding InitPlan, the Param will be evaluated on demand, right? Is the point of the new node to make sure that the Param gets re-evaluated when needed? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: