Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bfq7R-0002C8-M1 for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Sep 2016 15:11:01 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bfq7R-0007dz-6Q for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Sep 2016 15:11:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bfq7Q-0007d3-7R for pgsql-hackers@postgresql.org; Fri, 02 Sep 2016 15:11:00 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bfq7N-0002yk-L8 for pgsql-hackers@postgresql.org; Fri, 02 Sep 2016 15:10:59 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u82FAs5Y011836; Fri, 2 Sep 2016 11:10:54 -0400 From: Tom Lane To: Kevin Grittner cc: Andres Freund , Robert Haas , "pgsql-hackers@postgresql.org" Subject: Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling) In-reply-to: References: <20160523005327.v2tr7obytitxcnna@alap3.anarazel.de> <20160822214023.aaxz5l4igypowyri@alap3.anarazel.de> <20160902141110.6xciuntt5h4i6eni@alap3.anarazel.de> <20160902142023.ktgvv4ksnqinqr74@alap3.anarazel.de> <10163.1472826300@sss.pgh.pa.us> <10998.1472827875@sss.pgh.pa.us> Comments: In-reply-to Kevin Grittner message dated "Fri, 02 Sep 2016 10:01:39 -0500" Date: Fri, 02 Sep 2016 11:10:54 -0400 Message-ID: <11835.1472829054@sss.pgh.pa.us> X-Pg-Spam-Score: -3.4 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Kevin Grittner writes: > On Fri, Sep 2, 2016 at 9:51 AM, Tom Lane 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. Also, before getting too high and mighty with users who expect "select * from table" to produce rows in a predictable order, you should reflect on the number of places in our regression tests that assume exactly that ... regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers