Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling)
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org
Date: 2016-09-13T17:55:52Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > On September 13, 2016 9:07:35 AM PDT, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> I'd like to go ahead and push this, since it's a necessary prerequisite >> for either approach we might adopt for the rest of the patch series, >> and the improved error reporting and avoidance of expensive >> expression_returns_set searches make it a win IMO even if we were not >> planning to do anything more with SRFs. > Can't look are the code just now, on my way to the airport for pgopen, but the idea sounds good to me. OK, I went ahead and pushed it. We can tweak later if needed. regards, tom lane
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