Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d9Dqh-0006r6-Q5 for pgsql-hackers@arkaria.postgresql.org; Fri, 12 May 2017 16:55:27 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d9Dqh-0004bM-Ck for pgsql-hackers@arkaria.postgresql.org; Fri, 12 May 2017 16:55:27 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d9Dqg-0004YV-Pj for pgsql-hackers@postgresql.org; Fri, 12 May 2017 16:55:26 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d9Dqe-0007vb-EV for pgsql-hackers@postgresql.org; Fri, 12 May 2017 16:55:25 +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 v4CGtDfX024056; Fri, 12 May 2017 12:55:13 -0400 From: Tom Lane To: Robert Haas cc: Heikki Linnakangas , pgsql-hackers Subject: Re: eval_const_expresisions and ScalarArrayOpExpr In-reply-to: References: <3be3b82c-e29c-b674-2163-bf47d98817b1@iki.fi> <23186.1494516060@sss.pgh.pa.us> <4b14a9a5-01c2-4042-3ec9-cf27149302a5@iki.fi> <22029.1494605094@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Fri, 12 May 2017 12:51:51 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <24054.1494608113.1@sss.pgh.pa.us> Date: Fri, 12 May 2017 12:55:13 -0400 Message-ID: <24055.1494608113@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) 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 Robert Haas writes: > On Fri, May 12, 2017 at 12:04 PM, Tom Lane wrote: >> Actually, I now remember that I wrote that while at Salesforce (because >> they'd run into the problem that constant ArrayRef expressions weren't >> simplified). So that means it's been languishing in a git branch for >> *two* years. I'm kind of inclined to push it before it gets forgotten >> again ;-) > You will probably not be surprised to hear that I think this is a > feature and thus subject to the feature freeze currently in effect. [ shrug ] Sure. I'll do what I should have done then, which is stick it into the next CF list. If you intend to also object to my proposed get_attstatsslot refactoring, please do that promptly. That one I think is bug-proofing. 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