Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bfpQO-0000FO-V5 for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Sep 2016 14:26:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bfpQO-00042b-BD for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Sep 2016 14:26:32 +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 1bfpP0-0001DL-EI for pgsql-hackers@postgresql.org; Fri, 02 Sep 2016 14:25:06 +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 1bfpOx-0001zl-Ro for pgsql-hackers@postgresql.org; Fri, 02 Sep 2016 14:25:05 +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 u82EP0HB010164; Fri, 2 Sep 2016 10:25:00 -0400 From: Tom Lane To: Andres Freund cc: Kevin Grittner , Robert Haas , "pgsql-hackers@postgresql.org" Subject: Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling) In-reply-to: <20160902142023.ktgvv4ksnqinqr74@alap3.anarazel.de> References: <20160523005327.v2tr7obytitxcnna@alap3.anarazel.de> <20160822214023.aaxz5l4igypowyri@alap3.anarazel.de> <20160902141110.6xciuntt5h4i6eni@alap3.anarazel.de> <20160902142023.ktgvv4ksnqinqr74@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Fri, 02 Sep 2016 07:20:23 -0700" Date: Fri, 02 Sep 2016 10:25:00 -0400 Message-ID: <10163.1472826300@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 Andres Freund writes: > Oh, and we've previously re-added that based on > complaints. C.f. d543170f2fdd6d9845aaf91dc0f6be7a2bf0d9e7 (and others > IIRC). That one wasn't about row order per se, but I agree that people *will* bitch if we change the behavior, especially if we don't provide a way to fix it. ORDER BY is not a useful suggestion when there is nothing you could order by to get the old behavior. 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