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: Kevin Grittner <kgrittn@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2016-09-02T14:20:23Z
Lists: pgsql-hackers
On 2016-09-02 07:11:10 -0700, Andres Freund wrote: > On 2016-09-02 09:05:35 -0500, Kevin Grittner wrote: > > On Fri, Sep 2, 2016 at 3:31 AM, Robert Haas <robertmhaas@gmail.com> wrote: > > > On Tue, Aug 23, 2016 at 3:10 AM, Andres Freund <andres@anarazel.de> wrote: > > > > >> =# SELECT * FROM few, ROWS FROM(generate_series(1,3)); > > >> ┌────┬─────────────────┐ > > >> │ id │ generate_series │ > > >> ├────┼─────────────────┤ > > >> │ 1 │ 1 │ > > >> │ 2 │ 1 │ > > >> │ 1 │ 2 │ > > >> │ 2 │ 2 │ > > >> │ 1 │ 3 │ > > >> │ 2 │ 3 │ > > >> └────┴─────────────────┘ > > >> (6 rows) > > >> surely isn't what was intended. So the join order needs to be enforced. > > > > > > In general, we've been skeptical about giving any guarantees about > > > result ordering. > > Well, it's historically how we behaved for SRFs. I'm pretty sure that > people will be confused if > SELECT generate_series(1, 10) FROM sometbl; > suddenly returns rows in an order that reverse from what > generate_series() returns. Oh, and we've previously re-added that based on complaints. C.f. d543170f2fdd6d9845aaf91dc0f6be7a2bf0d9e7 (and others IIRC).
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