Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dFKlY-0002jg-Q6 for pgsql-hackers@arkaria.postgresql.org; Mon, 29 May 2017 13:31:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dFKlX-0004lU-Ok for pgsql-hackers@arkaria.postgresql.org; Mon, 29 May 2017 13:31:23 +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 1dFKlW-0004lJ-TK for pgsql-hackers@postgresql.org; Mon, 29 May 2017 13:31:22 +0000 Received: from mail-wm0-x231.google.com ([2a00:1450:400c:c09::231]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dFKlT-0006gE-12 for pgsql-hackers@postgresql.org; Mon, 29 May 2017 13:31:22 +0000 Received: by mail-wm0-x231.google.com with SMTP id d127so59745590wmf.0 for ; Mon, 29 May 2017 06:31:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=nYhG78wwnz+WtCFvxmwZ8OeTbkaj2KrlstZcyT6MMxo=; b=cpasmj4rqgNns6f0K9LfEpR2ArIV/C0QMCzmeoxj/J6MryAGHOaBL5nswY0XmGfzDe pobRTFmKGKukReUEgju8dZj6XXwokcbIRcLLTyK/WXMkeTQben5DHby3Jw4I4HFLDHXp 838MsK3uCLq05nFbHKDVf5i8TLuK+NX9djPy+4X8ezVbRA436U8iI9Ky7PcJv70nt7w1 Zv4Zfafd7b/N6zFo+/UlvunFxR9ypCAVcHh4Bxqm0e4hYF3A5u3rKmgNC1UTTVnmCfjA fJ89Y6JnynN2EmCNL0ONoWkIYrvz9JYFi2EhIWpnHJJchQkts9ChckX3TXtCwPelQ3hg 5PQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=nYhG78wwnz+WtCFvxmwZ8OeTbkaj2KrlstZcyT6MMxo=; b=Aynn+w4recp4FLZtRJDr1lBu9lCRy0NRiOrVy9ABjFVIBnMLHTChOyiG23DK9yg0cu F3Wuzk6qvV82hS8JlGQP5Qj9j6IM93UB9eRl9lQXkAQam/w1pNvxwPwnPEapD+6gYUGL 7G4lOHy4DVJq8Gz/TllEWbHbqQF91QxvWU6QA3GPd30fm2FIq1NUQSqOlGnZIn75P5QQ Ng3AmnBuicLB3PiUMaqK5O1FzYWgCB37oPbl+B4Bh3VDLfNYOlZMfaQuldg9Js9mjzgD 7ymXBNf6Oo8ZHq+D9sln73jO0JLPaz/jVqsLx/2r5uc65KmyaJoaC3yl/jrdJ69s7kzB YbRA== X-Gm-Message-State: AODbwcDpg0/vKEuuiig6o1ctx/sMW7HiVHr5fhCIzUM6UCBG4XPb/0+7 F5Q2zK+pihtmnvKPDBx5ACctzV7Cq35QEoVgVGvaHMaSFo0AR11Xz3ETaWEmvX8tJRnhjOXDRLP nG3SbIVyHCFLJ3remLOaJp9WBpqK3ApPF9WTvu0Hzl4JM9yQgvl+PfrR8N5GkUKl0kQ1vDjbJZh 28 X-Received: by 10.223.161.30 with SMTP id o30mr10093648wro.186.1496064677146; Mon, 29 May 2017 06:31:17 -0700 (PDT) Received: from [10.108.24.30] ([104.222.149.132]) by smtp.gmail.com with ESMTPSA id z12sm13323439wrb.41.2017.05.29.06.31.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 May 2017 06:31:16 -0700 (PDT) Subject: Re: Inconsistent syntax for NumericOnly grammar production To: Tom Lane , pgsql-hackers@postgreSQL.org References: <30908.1496006184@sss.pgh.pa.us> From: Vik Fearing Organization: 2ndQuadrant France Message-ID: <9dd9dbcf-69aa-a093-e1d1-64007306678b@2ndquadrant.com> Date: Mon, 29 May 2017 15:31:15 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <30908.1496006184@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) 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 On 05/28/2017 11:16 PM, Tom Lane wrote: > The inconsistency here means that you can do, for example, > > regression=# set random_page_cost = +4; > SET > regression=# set random_page_cost = 4.2; > SET > > but not > > regression=# set random_page_cost = +4.2; > ERROR: syntax error at or near "4.2" > LINE 1: set random_page_cost = +4.2; > ^ > Any objections to allowing "+ FCONST" here? I'm inclined to > fix this and back-patch it as well. Seems like the right thing to do; no objections here. -- Vik Fearing +33 6 46 75 15 36 http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers