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 1qBoh6-0007cg-Nl for pgsql-hackers@arkaria.postgresql.org; Wed, 21 Jun 2023 03:39:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qBoh3-00087v-Cn for pgsql-hackers@arkaria.postgresql.org; Wed, 21 Jun 2023 03:39:41 +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 1qBoh3-00087l-3S for pgsql-hackers@lists.postgresql.org; Wed, 21 Jun 2023 03:39:41 +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 1qBogz-003k7O-P9 for pgsql-hackers@postgresql.org; Wed, 21 Jun 2023 03:39:40 +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 35L3dVh33685080; Tue, 20 Jun 2023 23:39:31 -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> <2823519.1687137059@sss.pgh.pa.us> Comments: In-reply-to Michael Paquier message dated "Wed, 21 Jun 2023 09:02:35 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3685078.1687318771.1@sss.pgh.pa.us> Date: Tue, 20 Jun 2023 23:39:31 -0400 Message-ID: <3685079.1687318771@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > As a whole, I'd like to think that this is an improvement even for > stable branches with these weird isspace() handlings, so I'm OK with > the current status in all the branches. Sounds like we're all content with that. > There's an argument about \v, > IMO, but I won't fight hard for it either even if it would be more > consistent with the way array values are handled. I'd be okay with adding \v to the set of whitespace characters in scan.l and scanner_isspace (and other affected places) for v17. Don't want to back-patch it though. regards, tom lane