Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling)
Kevin Grittner <kgrittn@gmail.com>
From: Kevin Grittner <kgrittn@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2016-09-02T16:08:02Z
Lists: pgsql-hackers
On Fri, Sep 2, 2016 at 10:10 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Kevin Grittner <kgrittn@gmail.com> writes: >> On Fri, Sep 2, 2016 at 9:51 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> regression=# select *, generate_series(1,3) from int8_tbl; > >> I'm sure that you realize that running a query of that form twice >> against a table with more than one heap page could result in rows >> in a different order, even if no changes had been made to the >> database (including no vacuum activity, auto- or otherwise). > > You missed my point: they might complain about the generate_series > output not being in the order they expect, independently of what > the table rows are. I didn't miss it, I just never thought that anyone would care about a secondary sort key if the primary sort key was random. I have trouble imagining a use-case for that. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
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