Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7y05-008eGS-En for pgsql-general@arkaria.postgresql.org; Fri, 17 May 2024 13:51:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s7y05-00E4w9-A6 for pgsql-general@arkaria.postgresql.org; Fri, 17 May 2024 13:51:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7y04-00E4w1-Vd for pgsql-general@lists.postgresql.org; Fri, 17 May 2024 13:51:56 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7y02-000fbR-Lw for pgsql-general@lists.postgresql.org; Fri, 17 May 2024 13:51:55 +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 44HDpnHs2388206; Fri, 17 May 2024 09:51:49 -0400 From: Tom Lane To: Troels Arvin cc: pgsql-general@lists.postgresql.org Subject: Re: utf8 vs UTF-8 In-reply-to: References: Comments: In-reply-to Troels Arvin message dated "Fri, 17 May 2024 14:44:24 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2388204.1715953909.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 17 May 2024 09:51:49 -0400 Message-ID: <2388205.1715953909@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Troels Arvin writes: > In a Postgres installation, I have databases where the locale is = > slightly different. Which one is correct? Excerpt from "psql --list": > =C2=A0test1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 | loc_test | UTF8=C2=A0= =C2=A0=C2=A0=C2=A0 | libc=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 | en_US.UTF-8 | = > en_US.UTF-8 > =C2=A0test3=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 | troels=C2=A0=C2=A0 | = UTF8=C2=A0=C2=A0=C2=A0=C2=A0 | libc=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 | en_US.utf8 | = > en_US.utf8 On most if not all platforms, both those spellings of the locale names will be taken as valid. You might try running "locale -a" to get an idea of which one is preferred according to your current libc installation ... but TBH, I doubt it's worth worrying about. regards, tom lane