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 1nV1vd-00077A-BT for pgsql-committers@arkaria.postgresql.org; Fri, 18 Mar 2022 02:01:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nV1vb-0001te-6S for pgsql-committers@arkaria.postgresql.org; Fri, 18 Mar 2022 02:01:19 +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 1nV1va-0001sb-Vm for pgsql-committers@lists.postgresql.org; Fri, 18 Mar 2022 02:01:18 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nV1vY-0006Qd-Iq for pgsql-committers@lists.postgresql.org; Fri, 18 Mar 2022 02:01:17 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 79B7F3201DDC; Thu, 17 Mar 2022 22:01:15 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 17 Mar 2022 22:01:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; bh=fc/BmxCX9k14Wf3skUKfmqTNip2gHGALQS8LK4 PlM5s=; b=YgCD0v0LbJ8h//gR5E7AQjsu9KjPXdbIDm2/j/yBG4PsmcQx3m7sXQ w6+BOmg3D+Wcskxj/jO+lrm27E44mCBDqb/q4SlxE+eZD/zvQrz4pmqQdgsAsUjB Sljbwfp3n5Y5A+H6oeukwp31dJnsS9FQLenSBYL46P14AYqVlKFTGsVeZut+iJyz /vuzOAtrajTZSK+1enphDvdUJFVJFP2m8iSnLtjIPp/76MZQTA2w43K3iVG55Jta FMpI1JQlq6RD/7IXQ5S8dQN5KngToqyK9Ybc2klxFj0xOpa/vQTkM8YhHG6nLnYz 00aCVrFytUGPMAT54GCwFVjyRu1nt0Yg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc: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=fc/BmxCX9k14Wf3sk UKfmqTNip2gHGALQS8LK4PlM5s=; b=EZYxCdKVPMvm1mJBupVa3QcoXPphsVHzw KPx5gEaStTfqHYQLEIWb3/Io0ADKcNpggep5aW34ZSdrbEh3eTY4BINsDJS3/lE8 VOAQsdzwUBd5SteWQsrlJEQjDuSpdqk8V4jraO9tZkyt/HDMF/v3+R1fihP4HvNK 58Ll1vgLVMVlS/yCwOoEJvNlxNjt1kaLdYZt9jx5maweyTHL2s+4EgXKcciS1uHT IPw3Ej+717M+pdEXGpsRvZgoAR+Npcg6clFN8Evv2hA+Bov8vY6gBw/4Pmrok80p UCv/A65k1IGWbWD4Vkx6b5wn3X6LmdhEOzaUAkIhVg4CvB9rMiGpA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudefhedggedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdlfeehmdenucfjughrpeffhffvuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeffudeffeelgffhkedukeekvedv udfgieetkeekudelfeevhffhffdtudffieeutdenucffohhmrghinhepphhoshhtghhrvg hsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 17 Mar 2022 22:01:13 -0400 (EDT) Date: Fri, 18 Mar 2022 11:01:11 +0900 From: Michael Paquier To: Peter Eisentraut Cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Add option to use ICU as global locale provider Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qiX71QxY8n7bgMrD" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --qiX71QxY8n7bgMrD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Peter, On Thu, Mar 17, 2022 at 10:22:32AM +0000, Peter Eisentraut wrote: > Add option to use ICU as global locale provider >=20 > This adds the option to use ICU as the default locale provider for > either the whole cluster or a database. New options for initdb, > createdb, and CREATE DATABASE are used to select this. >=20 > Since some (legacy) code still uses the libc locale facilities > directly, we still need to set the libc global locale settings even if > ICU is otherwise selected. So pg_database now has three > locale-related fields: the existing datcollate and datctype, which are > always set, and a new daticulocale, which is only set if ICU is > selected. A similar change is made in pg_collation for consistency, > but in that case, only the libc-related fields or the ICU-related > field is set, never both. FYI, prion is complaining here: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dprion&dt=3D2022-0= 3-18%2001%3A43%3A13 Some details: # Failed test 'fails for invalid ICU locale: matches' # at t/001_initdb.pl line 107. # '2022-03-18 01:54:58.563 UTC [504] FATAL: could # not open collator for locale "@colNumeric=3Dlower": # U_ILLEGAL_ARGUMENT_ERROR -- Michael --qiX71QxY8n7bgMrD Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmIz5+cACgkQnvQgOdby QH0Ztg/6AjiMWjlY7LlO7DoHSwXw+Vj6sd5jGpwdBT33WviIr3femsy8WWyLBrhE H0nYMLEs1WSIvNsQ30WDYjiJV99azcwAkAAybfXG4KVyp9YYOWXQ3V1RNYfNFxRy bQ//TQJaB9KrRUaXeerwgRhqAQeoM5WnpEpFnbgmFUtp21J6ABvSlS6Z91QpfcEU ftUqOj2KCBURzhYcwwAKiIqIHQK/eCIzA+7PdNtOQiLT+ntAYZdzxPPVQ6Z72/KW OWYGXUavUiO9oFrWIunKL9fkikKUShYruHfLOKncJDEwBcfpBOmYu0CrgOpnG/F6 JGIN03n52mSoC1JlhSO6Jx2ktrfD26+QtXQOR8VPvBjik51LKAXtIDe4Sl6DkR8a fEOR3mC7PaN6Z4UHm3DQ9cAZg/fPEDl59fQPxOW5iJJbSuw6uitNLQUK4TxEsICz HK/yWJoHJ4oQk/d0nDSl2Sud9Qo8ZKi598VPnrL8itXUgMmQ2bRAWXjrMGd9iHZm YDXdfWFAmAkPuhCDhA6JopMF+92E9rr4NUDWbOr6N1qft1Gl3/QRPg57Ps8FF9Cb o7iop1xCI+S7XOv6520jpLMyT9xVQTVeUJkdIa5V215RB+BGYZEo23TvTMnkWTIN dIraR53YKuDdfxbi/dbAKgj3rZCIUpIqt3C+/45lwOpDXMUxCYM= =6ftb -----END PGP SIGNATURE----- --qiX71QxY8n7bgMrD--