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 1pwPCN-0007M5-3X for pgsql-general@arkaria.postgresql.org; Tue, 09 May 2023 15:24:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pwPCL-0000WA-Po for pgsql-general@arkaria.postgresql.org; Tue, 09 May 2023 15:24:17 +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 1pwPCL-0000W0-Eg for pgsql-general@lists.postgresql.org; Tue, 09 May 2023 15:24:17 +0000 Received: from wnew2-smtp.messagingengine.com ([64.147.123.27]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pwPCI-001bI1-Gg for pgsql-general@lists.postgresql.org; Tue, 09 May 2023 15:24:16 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailnew.west.internal (Postfix) with ESMTP id 787B52B067FD; Tue, 9 May 2023 11:24:12 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 09 May 2023 11:24:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id: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; t=1683645852; x= 1683653052; bh=SnRchAbpAnZxP9rcGcAK18jKWg0G3ZaRRTn/DiecNsQ=; b=c MzpgshhaIYvtySTBraiuSQu4nKj5jRTXa5JenxWUXCRdihcHARKa0CIIQDkmaWJ4 fJ+eEMwdgzCqAbx6JAGX07t2tIKvMGjJGbwpk3cSuj/GlK/g7VLIMbzWUZjYM3ZC 4FNCcpUfZGr2Mi77A6Ut2ICEa1nMBosnbH7dVnlBI6a9q+M8Ysj957S3AwWmx89r gOcTzXPRyaVLaxGDCZOXoQr9JUUIHuXCmysQX+a5e43yD8CwR+RbaFWshjQ8Z/KA j6vDG21591l8mKes8lt7xuljyi9NuvK2E/OJ4LoTxa/vVozHKZfITSIsVMzqyBY8 0VeJ1gq+TH6i1e3x8IGaw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeeguddgudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthejredttdefjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvg hrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepfeejgeehteeuhfevvedu leeufedtjeetiefftedvudfhtdeifefgueettdevgefgnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhht segvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 9 May 2023 11:24:11 -0400 (EDT) Message-ID: Date: Tue, 9 May 2023 17:24:09 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: ICU, locale and collation question Content-Language: en-US To: Oscar Carlberg , Laurenz Albe , pgsql-general@lists.postgresql.org References: <2a1de395-c69a-3dae-4459-dbdb633df637@fortnox.se> <4210aaef-06ff-628e-a2c8-a1a4bf28d278@fortnox.se> From: Peter Eisentraut In-Reply-To: <4210aaef-06ff-628e-a2c8-a1a4bf28d278@fortnox.se> 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 09.05.23 08:54, Oscar Carlberg wrote: > Our initdb setup would then look like this for compatibility; > -E 'UTF-8' > --locale-provider=icu > --icu-locale=sv-SE-x-icu > --lc_monetary=sv_SE.UTF-8 > --lc-numeric=sv_SE.UTF-8 > --lc-time=sv_SE.UTF-8 > --lc-messages=en_US.UTF-8 > > Should we still provide createdb with --lc-collate=C and --lc-ctype=C, > or should we set those to sv_SE.UTF-8 as well? You should set those to something other than C. It doesn't matter much what exactly, so what you have there is fine. Setting it to C would for example affect the ability of the text search functionality to detect words containing non-ASCII characters.