Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pMsZ8-0008L1-0Y for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Jan 2023 15:28:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pMsZ6-0003ys-Sm for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Jan 2023 15:28:56 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pMsZ6-0003yh-Iv for pgsql-hackers@lists.postgresql.org; Tue, 31 Jan 2023 15:28:56 +0000 Received: from wnew2-smtp.messagingengine.com ([64.147.123.27]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pMsZ3-0007fY-In for pgsql-hackers@postgresql.org; Tue, 31 Jan 2023 15:28:55 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.west.internal (Postfix) with ESMTP id 633292B0685E; Tue, 31 Jan 2023 10:28:51 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 31 Jan 2023 10:28:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1675178930; x= 1675186130; bh=rSFJeTyzC+l3zNrEU4M+C2N7kkJElj6VK6Vfyv8ZR2Y=; b=O TY6DbtHZ/ZMwoQQ+BejrHt7iiBfIMXB2aMZlU/SdS7wGqGDtlMGCzPUfzLmE3vHf F5bW0yjH0NgUCarqab7Yi9okI9C2/fE+cVkjnY6Hkzyx96/D4eiBnXcB4MOxpqyf ihnOjpNddvEI0ZPhWIz5R5T2nxGeM7ENBrSjWI7h9Ihc60FbqfcjFM0h0ILFnq+J LBBlNsxdrO/8CI9gNutncNsI4A058Yzf9jdlrrK4Jetk0logmAcjITFwpqqPRedG ohLIOjBOfum9EmrOj7KJ7CNdGcZBW0ohxpq5u5Z+bHILD60WfWB4DvDsh2MWBP5D SrKaAQQeeFQK11EQihZBw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudefgedgjeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeehleffgeegudejteei hfelteduvdeifffhffdvjedvffegjeekudeludehudeifeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 31 Jan 2023 10:28:49 -0500 (EST) Message-ID: Date: Tue, 31 Jan 2023 16:28:48 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Underscores in numeric literals Content-Language: en-US To: Dean Rasheed , Andrew Dunstan Cc: Tom Lane , pgsql-hackers References: <84aae844-dc55-a4be-86d9-4f0fa405cc97@enterprisedb.com> <4015800.1672152932@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 23.01.23 21:45, Dean Rasheed wrote: > On Wed, 4 Jan 2023 at 09:28, Dean Rasheed wrote: >> >> In addition, I think that strip_underscores() could then go away if >> numeric_in() were made to handle underscores. >> >> Essentially then, that would move all responsibility for parsing >> underscores and non-decimal integers to the datatype input functions, >> or their support routines, rather than having it distributed. > > Here's an update with those changes. This looks good to me. Did you have any thoughts about what to do with the float types? I guess we could handle those in a separate patch?