Subject: Re: Names of encodings, lc_collate, lc_ctype
To: pgsql-admin@lists.postgresql.org
References: <3da4af02269b44a18b56a070af0bca18@jakobs.com>
 <810.1562765208@sss.pgh.pa.us>
From: Ron <ronljohnsonjr@gmail.com>
Message-ID: <9f1b3251-87a1-3fde-e51f-69010c181258@gmail.com>
Date: Wed, 10 Jul 2019 08:39:40 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <810.1562765208@sss.pgh.pa.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk

On 7/10/19 8:26 AM, Tom Lane wrote:
> Holger Jakobs <holger@jakobs.com> writes:
>>     CREATE DATABASE db1 WITH TEMPLATE = template0 ENCODING = 'UTF8'
>> LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8';
>> which causes trouble on a PostgreSQL 10 or 11 on an Ubuntu 18.04 machine
>>     ungültiger Locale-Name: »en_US.UTF-8«  (meaning 'illegal locale name')
> Hmm, does "locale -a" show that you have en_US installed?
>
> It's basically on the platform's libc to say whether the values for
> LC_COLLATE and LC_CTYPE are valid.  In my experience, glibc is quite
> forgiving about how the encoding suffix is spelled, so I'm wondering
> if your destination machine is simply lacking the locale definition.

My Ubuntu 18.04 system (upgraded from 16.04) has these:
C
C.UTF-8
en_US.utf8
POSIX


-- 
Angular momentum makes the world go 'round.