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 1nVIIt-0002XS-8C for pgsql-committers@arkaria.postgresql.org; Fri, 18 Mar 2022 19:30:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nVIIs-0004Ld-1W for pgsql-committers@arkaria.postgresql.org; Fri, 18 Mar 2022 19:30:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nVIIr-0004LU-Q2 for pgsql-committers@lists.postgresql.org; Fri, 18 Mar 2022 19:30:25 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nVIIp-0006HW-F7 for pgsql-committers@lists.postgresql.org; Fri, 18 Mar 2022 19:30:24 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id D59165C018A; Fri, 18 Mar 2022 15:30:22 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Fri, 18 Mar 2022 15:30:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=J+0twTBDT8JdpdmEm+c6oluzWEkhb45k7R0uwjwPy AE=; b=npg66duTrfbZqTaQOqC9lHFS/nadteGlB2BN3tQD3hAsh6Sp4b5a8tcxO ndhqiZyhncEa9UkRqKsDNGXNRzsgurHva2o2SxhwnLK1Wd+YVvQmM2vSPDViBIoO ucooSSMnsu7+2NZTKBpAZg0ocXLzcVH2btyJHa1sp2ZBbUIrCfG3g5e4ynfb/bji 8V5LE8jn415GUE6iXZWLB7J9+Zbqe8hdVvoTALxwwXq6hC4yWI5YfqgoXHa0puGn FYQJ9LjWvj46WpKTh/JevFTKseIBqGbwRucHSn/4iX4vdfs8DcWhI2zp/J+udqnN BWa82bfWmmYrcop9CS1OPMZ+QzHBg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudefiedguddvjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveev udelueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 18 Mar 2022 15:30:21 -0400 (EDT) Message-ID: <9cbb672e-a33f-3102-4aaf-758495f7a237@enterprisedb.com> Date: Fri, 18 Mar 2022 20:30:21 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: pgsql: Add option to use ICU as global locale provider Content-Language: en-US To: Tom Lane Cc: Julien Rouhaud , Michael Paquier , pgsql-committers@lists.postgresql.org References: <20220318031244.tu3wwlyxxabzq3iu@jrouhaud> <1069623.1647616024@sss.pgh.pa.us> <1114934.1647624581@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: <1114934.1647624581@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 18.03.22 18:29, Tom Lane wrote: > 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? This is an appropriate solution, I think.