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 1p0WdQ-0003qZ-Im for pgsql-hackers@arkaria.postgresql.org; Wed, 30 Nov 2022 23:37:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p0WdP-0002ZN-FQ for pgsql-hackers@arkaria.postgresql.org; Wed, 30 Nov 2022 23:36:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p0WdP-0002ZE-6I for pgsql-hackers@lists.postgresql.org; Wed, 30 Nov 2022 23:36:59 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p0WdG-0005Fi-6O for pgsql-hackers@postgresql.org; Wed, 30 Nov 2022 23:36:58 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 2AUNaljJ1467948; Wed, 30 Nov 2022 18:36:47 -0500 From: Tom Lane To: David Rowley cc: Dean Rasheed , John Naylor , Peter Eisentraut , pgsql-hackers Subject: Re: Non-decimal integer literals In-reply-to: References: <0f37d2ec-6689-4d23-7ba5-4d2a73c2666f@enterprisedb.com> <577603ec-787b-61b8-23a2-1bd0457ed1c7@enterprisedb.com> <2317133.1643155358@sss.pgh.pa.us> <97aa22d7-b80f-efa1-f368-3dbf73a15980@enterprisedb.com> <071c40f2-15cf-5db3-8799-dbac041bb881@enterprisedb.com> <791aee01-f488-0706-2694-08c5b57a3bdd! @enterprisedb.com> Comments: In-reply-to David Rowley message dated "Thu, 01 Dec 2022 12:11:56 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1467946.1669851407.1@sss.pgh.pa.us> Date: Wed, 30 Nov 2022 18:36:47 -0500 Message-ID: <1467947.1669851407@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk David Rowley writes: > I agree that it should be a separate patch. But thinking about what > Tom mentioned in [1], I had in mind this patch would need to wait > until the new standard is out so that we have a more genuine reason > for breaking existing queries. Well, we already broke them in v15: that example now gives regression=# select 0x42e; ERROR: trailing junk after numeric literal at or near "0x" LINE 1: select 0x42e; ^ So there's probably no compatibility reason not to drop the other shoe. regards, tom lane