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 1pFzf8-0000he-Pd for pgsql-general@arkaria.postgresql.org; Thu, 12 Jan 2023 15:38:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pFzf7-00047a-0t for pgsql-general@arkaria.postgresql.org; Thu, 12 Jan 2023 15:38:41 +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 1pFzf6-00047Q-Io for pgsql-general@lists.postgresql.org; Thu, 12 Jan 2023 15:38:40 +0000 Received: from mail-ej1-x631.google.com ([2a00:1450:4864:20::631]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pFzf4-00028v-6p for pgsql-general@lists.postgresql.org; Thu, 12 Jan 2023 15:38:39 +0000 Received: by mail-ej1-x631.google.com with SMTP id ud5so45753381ejc.4 for ; Thu, 12 Jan 2023 07:38:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=MQTxefyOeKh+03eLo4wX6ZdEnubcyb2SK9Dv3NFmND4=; b=5BJE9XhMyWAAw4MqCmn1NbNwix+4nty9990X2mTNaXLIrJh7lCiDhOBoo/FceNMa1J xVQmuiL0eD+/XE6i8TNULBruXXajn8jrJOZhnG81ayvi0mbwf6v2+PC/OnmzhqHsOzPO 5Jm6x0jeKq7HcrK236FjuyDjGU5+j/A8NLn7dlEYBePURgPxu+6H0KCWj757xK9nm1Hu huut+nZcAgqfvSVToDmqUZcRtQqQo0iaAEpaxuexbrMSdmnYzsuyXQJBHIAQ1lLV+qSS uZI/Am/RcAi7FuRE1/flIbuHB7comDgXd9xoOvn0HsSeg+ioRgLsU/2N2DjKN34OJLSD xsUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=MQTxefyOeKh+03eLo4wX6ZdEnubcyb2SK9Dv3NFmND4=; b=JS0uEs4faMO9edTW8BeNIEXGI0/6awyXCpKiscjn/r33xIWrQP8EyztH2RkUQFVTyh ixLNiQ2LVL1YZgx9KNTXNTZGy0lPNfQzbmUkTcpmBVh9oFxc6nvua2cONPvSfaOZRIy7 spsb9qm+p4YJVU3kfmaqDYiGeMIVXiv46hcrIpxi9Jh3iiex84GzQfCjDIyplmD5g3Mj 51XsPDnTHtx6T7198BwJflYDeCyh2tATLEZ9Ff5SOuhdOlcEkA4mri+CcSNr0yy9ATiD VJGlqu41qoijl9Yi3r8l+6LEx+1IRsqMtC/xRsJiID5uA6CQ5mxZJ5Xb3OuBXVHaLUVg fmoA== X-Gm-Message-State: AFqh2kq3GMw6+500X5T8iL1GqSrcd4ctrL2KHmpA6RpzOhlhRvRMiKCH lj8cqwb/XRFePs9GlojuTwDCHQ== X-Google-Smtp-Source: AMrXdXtoGIfUL5wzUYslLAVbBGCVjJmhbw5QtAiWLcx3rMA5BfHPfWNNVRul6CXHvHoMoAan+mMqrg== X-Received: by 2002:a17:906:3c0d:b0:84d:34f0:f766 with SMTP id h13-20020a1709063c0d00b0084d34f0f766mr20287057ejg.75.1673537916829; Thu, 12 Jan 2023 07:38:36 -0800 (PST) Received: from dynamic-pd01.res.v6.highway.a1.net ([2001:871:5e:539:1b2c:c52a:475d:310c]) by smtp.gmail.com with ESMTPSA id la19-20020a170907781300b007aee7ca1199sm7569812ejc.10.2023.01.12.07.38.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 12 Jan 2023 07:38:36 -0800 (PST) Message-ID: <665febd71c7fc4237020a96eb2f59fe548a28385.camel@cybertec.at> Subject: Re: default icu locale for new databases (PG15) From: Laurenz Albe To: Robert =?ISO-8859-1?Q?Sj=F6blom?= , pgsql-general Date: Thu, 12 Jan 2023 16:38:35 +0100 In-Reply-To: <90631fa8-242d-806a-da9a-e53d6f5a93f7@fortnox.se> References: <90631fa8-242d-806a-da9a-e53d6f5a93f7@fortnox.se> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.3 (3.46.3-1.fc37) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 2023-01-12 at 15:56 +0100, Robert Sj=C3=B6blom wrote: > When initializing a new database server with a default collation, there= =20 > are a number of different locales available. What's the difference betwee= n >=20 > 1. se-x-icu > 2. se-SE-x-icu > 3. sv-SE-x-icu >=20 > ? And, perhaps more importantly, how do I future-proof this so that I'm= =20 > not making a decision today that will make my life worse when upgrading= =20 > from postgres 15 to 16+? For a database with Swedish collation, which=20 > option is "the best"? Or perhaps "the most foolproof"? Of the alternatives you list, only "sv-SE-x-icu" makes sense, because "se" stands for the S=C3=A1mi or Lapp language, not Swedish. You could choose between "sv-SE", "sv-FI" and "sv-AX", depending on whether you are located in Sweden, Finland or the =C3=85land Islands. I don't spea= k Swedish, so I don't know how different they are and how they differ from the generic= "sv". I don't think any of these Locales will go away in the forseeable future. Yours, Laurenz Albe