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 1nVGQ9-0003Hm-9t for pgsql-committers@arkaria.postgresql.org; Fri, 18 Mar 2022 17:29:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nVGQ8-00050h-4q for pgsql-committers@arkaria.postgresql.org; Fri, 18 Mar 2022 17:29:48 +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 1nVGQ7-00050X-Tx for pgsql-committers@lists.postgresql.org; Fri, 18 Mar 2022 17:29:47 +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 1nVGQ5-00077D-TZ for pgsql-committers@lists.postgresql.org; Fri, 18 Mar 2022 17:29:47 +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 22IHTffn1114935; Fri, 18 Mar 2022 13:29:41 -0400 From: Tom Lane To: Peter Eisentraut cc: Julien Rouhaud , Michael Paquier , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Add option to use ICU as global locale provider In-reply-to: <1069623.1647616024@sss.pgh.pa.us> References: <20220318031244.tu3wwlyxxabzq3iu@jrouhaud> <1069623.1647616024@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Fri, 18 Mar 2022 11:07:04 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1114933.1647624581.1@sss.pgh.pa.us> Date: Fri, 18 Mar 2022 13:29:41 -0400 Message-ID: <1114934.1647624581@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I found a different problem with src/test/icu/: it fails altogether if the prevailing locale is "C", because then the database encoding defaults to SQL_ASCII which our ICU code won't cope with. I'm not sure if that explains any of the buildfarm failures, but it broke my local build (yeah, I'm that guy). I un-broke it for the moment by forcing the test to use UTF8 encoding, but do we want to do anything smarter than that? regards, tom lane