Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling)
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Date: 2017-01-16T21:33:30Z
Lists: pgsql-hackers
Andres Freund wrote: > On 2017-01-16 16:04:34 -0300, Alvaro Herrera wrote: > > Andres Freund wrote: > > > On 2017-01-16 12:17:46 -0300, Alvaro Herrera wrote: > > > > Hmm. I wonder if your stuff could be used as support code for > > > > XMLTABLE[1]. > > > > > > I don't immediately see what functionality overlaps, could you expand on > > > that? > > > > Well, I haven't read any previous patches in this area, but the xmltable > > patch adds a new way of handling set-returning expressions, so it > > appears vaguely related. > > Ugh. That's not good - I'm about to remove isDone. Like completely. > That's why I'm actually working on all this, because random expressions > returning more rows makes optimizing expression evaluation a lot harder. Argh. > > These aren't properly functions in the current sense of the word, > > though. > > Why aren't they? Looks like it'd be doable to do so, at least below the > parser level? Hmm ... -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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