Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling)
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Date: 2017-01-16T03:29:52Z
Lists: pgsql-hackers
On 2016-10-31 09:06:39 -0700, Andres Freund wrote: > On 2016-09-14 19:28:25 -0400, Tom Lane wrote: > > Andres Freund <andres@anarazel.de> writes: > > > On 2016-09-12 19:35:22 -0400, Tom Lane wrote: > > Here's a draft patch that is just meant to investigate what the planner > > changes might look like if we do it in the pipelined-result way. > > Accordingly, I didn't touch the executor, but just had it emit regular > > Result nodes for SRF-execution steps. However, the SRFs are all > > guaranteed to appear at top level of their respective tlists, so that > > those Results could be replaced with something that works like > > nodeFunctionscan. > > > So I think we should continue investigating this way of doing things. > > I'll try to take a look at the executor end of it tomorrow. However > > I'm leaving Friday for a week's vacation, and may not have anything to > > show before that. > > Are you planning to work on the execution side of things? I otherwise > can take a stab... Doing so now. Andres
Commits
-
Remove obsoleted code relating to targetlist SRF evaluation.
- ea15e18677fc 10.0 landed
-
Doc: improve documentation of new SRF-in-tlist behavior.
- f13a1277aa2d 10.0 landed
-
Move targetlist SRF handling from expression evaluation to new executor node.
- 69f4b9c85f16 10.0 landed
-
Don't split up SRFs when choosing to postpone SELECT output expressions.
- d543170f2fdd 9.6.0 cited