Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bjrw8-0005h5-2U for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Sep 2016 17:56:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bjrw7-00068I-Li for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Sep 2016 17:55:59 +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 1bjrw6-00066w-PZ for pgsql-hackers@postgresql.org; Tue, 13 Sep 2016 17:55:58 +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 1bjrw4-0002md-4R for pgsql-hackers@postgresql.org; Tue, 13 Sep 2016 17:55:58 +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 u8DHtqC6016092; Tue, 13 Sep 2016 13:55:52 -0400 From: Tom Lane To: Andres Freund cc: pgsql-hackers@postgresql.org Subject: Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling) In-reply-to: <026547FB-DFAF-4106-BC58-7BAC52733A28@anarazel.de> References: <20160523005327.v2tr7obytitxcnna@alap3.anarazel.de> <20160822214023.aaxz5l4igypowyri@alap3.anarazel.de> <20160827214829.zo2dfb5jaikii5nw@alap3.anarazel.de> <24639.1473782855@sss.pgh.pa.us> <026547FB-DFAF-4106-BC58-7BAC52733A28@anarazel.de> Comments: In-reply-to Andres Freund message dated "Tue, 13 Sep 2016 09:25:05 -0700" Date: Tue, 13 Sep 2016 13:55:52 -0400 Message-ID: <16091.1473789352@sss.pgh.pa.us> X-Pg-Spam-Score: -4.2 (----) 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: > On September 13, 2016 9:07:35 AM PDT, Tom Lane 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers