Re: Names of encodings, lc_collate, lc_ctype

On 7/10/19 8:26 AM, Tom Lane wrote:
> Holger Jakobs <holger(at)jakobs(dot)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.