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 1qB3QG-00030u-Qx for pgsql-hackers@arkaria.postgresql.org; Mon, 19 Jun 2023 01:11:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qB3QF-0003je-Pc for pgsql-hackers@arkaria.postgresql.org; Mon, 19 Jun 2023 01:11:11 +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 1qB3QF-0003jV-H2 for pgsql-hackers@lists.postgresql.org; Mon, 19 Jun 2023 01:11:11 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qB3QB-003KhQ-QM for pgsql-hackers@postgresql.org; Mon, 19 Jun 2023 01:11:10 +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 35J1Axme2823520; Sun, 18 Jun 2023 21:10:59 -0400 From: Tom Lane To: Michael Paquier cc: Evan Jones , pgsql-hackers@postgresql.org Subject: Re: [PATCH] hstore: Fix parsing on Mac OS X: isspace() is locale specific In-reply-to: References: <2765603.1687106292@sss.pgh.pa.us> Comments: In-reply-to Michael Paquier message dated "Mon, 19 Jun 2023 08:28:43 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2823518.1687137059.1@sss.pgh.pa.us> Date: Sun, 18 Jun 2023 21:10:59 -0400 Message-ID: <2823519.1687137059@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > Another thing that I was wondering, though.. Do you think that there > would be an argument in being stricter in the hstore code regarding > the handling of multi-byte characters with some checks based on > IS_HIGHBIT_SET() when parsing the keys and values? What have you got in mind? We should already have validated encoding correctness before the text ever gets to hstore_in, and I'm not clear what additional checks would be useful. regards, tom lane