Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sUSZn-003Bvx-Fo for pgsql-sql@arkaria.postgresql.org; Thu, 18 Jul 2024 14:57:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sUSZk-00018N-AM for pgsql-sql@arkaria.postgresql.org; Thu, 18 Jul 2024 14:57:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sUSZk-00018E-1A for pgsql-sql@lists.postgresql.org; Thu, 18 Jul 2024 14:57:44 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sUSZi-000DaH-4V for pgsql-sql@lists.postgresql.org; Thu, 18 Jul 2024 14:57:43 +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 46IEveAA3709212; Thu, 18 Jul 2024 10:57:40 -0400 From: Tom Lane To: Bharani SV-forum cc: "David G. Johnston" , "pgsql-sql@lists.postgresql.org" , Frank Komsic Subject: Re: SQL statements error in pgsql 16 but not in pgsql 12 In-reply-to: <432596330.2235682.1721314214935@mail.yahoo.com> References: <151842168.569875.1721141786874@mail.yahoo.com> <432596330.2235682.1721314214935@mail.yahoo.com> Comments: In-reply-to Bharani SV-forum message dated "Thu, 18 Jul 2024 14:50:14 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3709210.1721314660.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 18 Jul 2024 10:57:40 -0400 Message-ID: <3709211.1721314660@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Bharani SV-forum writes: > tagged mean " add to something " > hope ur picture posted with the sql query, i can see asWHERE (lot =3D 19= 749OR lot=3D 19750)instead of = > WHERE (lot =3D 19749 OR lot=3D 19750) That's not a great choice of word. In any case, the point here is that the SQL standard requires some whitespace between a number and a following word, and starting from PG 15 we're enforcing that to reduce ambiguity. regards, tom lane