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 1s8Ku8-00Brwk-PU for pgsql-general@arkaria.postgresql.org; Sat, 18 May 2024 14:19:23 +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 1s8Ku8-006JoK-PW for pgsql-general@arkaria.postgresql.org; Sat, 18 May 2024 14:19:20 +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 1s8Ku8-006JoC-By for pgsql-general@lists.postgresql.org; Sat, 18 May 2024 14:19:20 +0000 Received: from home.borberg.arvin.dk ([194.45.76.153]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s8Ku4-000pL1-S1 for pgsql-general@lists.postgresql.org; Sat, 18 May 2024 14:19:18 +0000 Received: from localhost (localhost [127.0.0.1]) by arvin.dk (Postfix) with ESMTP id 855F527B5A; Sat, 18 May 2024 16:19:12 +0200 (CEST) X-Virus-Scanned: amavis at arvin.dk Received: from arvin.dk ([127.0.0.1]) by localhost (arvinserver4.home.borberg.arvin.dk [127.0.0.1]) (amavis, port 10024) with LMTP id aYUfFxQceRBT; Sat, 18 May 2024 16:19:11 +0200 (CEST) Received: from [192.168.2.160] (_gateway [192.168.1.1]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by arvin.dk (Postfix) with ESMTPSA id 9396627B59; Sat, 18 May 2024 16:19:11 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 arvin.dk 9396627B59 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arvin.dk; s=202311171; t=1716041951; bh=+lUGBrRaQLUqTSfquXfDeVwKiwrsCIS9DhPWh/AKY6s=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=GMBP3fnsFvB/ziEgqTrEBsjJgK/UJEDMBuJJUtwJKZmEQyioziV8rinCXTPl0nK39 vWSjyVg+S/vzG+MYObOgr6Qs93Gm0UsFrNwGbHNep3b6rnjwnNDcEkcWL8s0oi1SJQ QlXpaYmaAdYZhQIQztqBYfP++WJ9mgSfJAnEkkEBbanJ6JQJ+AGkw2zDxJEph6TXV9 HkRiYulskuwHTZWJrey7tjQBFd3e4tjM7gNkULuA5f51MYPZIMaikhlFdpWSAZkFGJ iMy0yqK2NGfgot1W4nHFvCuzONd6Dw0rDYnK1zn6VovDjZW+v9Zvcr/FzHefU23ydW NCCEU3LovDGDg== Message-ID: <8cd94f70-4075-408c-a60a-f16c11c8f93a@arvin.dk> Date: Sat, 18 May 2024 16:19:11 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: utf8 vs UTF-8 To: Hans Schou Cc: pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Troels Arvin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hellok Hans Schou wrote: >   > test3       | troels   | UTF8     | libc | en_US.utf8 |  en_US.utf8 [...] >   how did you create test3? For this example, I used specified it at creation time: CREATE DATABASE test3 TEMPLATE template0 LOCALE 'en_US.utf8'; In the real-world example I'm working with I'm unsure how the database was originally created. -- Troels