From: Tom Lane <tgl@sss.pgh.pa.us>
To: mail@localhorst.es
cc: pgsql-admin@lists.postgresql.org
Subject: Re: Different encodings and locales on one machine
In-reply-to: <a08646b59be303a9a3ffa21f72436b90@localhorst.es>
References: <a08646b59be303a9a3ffa21f72436b90@localhorst.es>
Comments: In-reply-to mail@localhorst.es
	message dated "Thu, 04 Mar 2021 09:40:26 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1360324.1614871773.1@sss.pgh.pa.us>
Date: Thu, 04 Mar 2021 10:29:33 -0500
Message-ID: <1360325.1614871773@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1360325.1614871773%40sss.pgh.pa.us>
Precedence: bulk

mail@localhorst.es writes:
> at the moment I am running two different PostgreSQL (12) servers on one 
> Ubuntu 20.04 machine.
> For server one I need WIN1252 encoding with "de_DE.cp1252" locales set.
> For server two I need UTF8 encoding, but also with "de_DE.cp1252" 
> locales set.

This statement is nonsensical.  The second component of the locale name
is precisely the encoding that the locale is meant to be used with.
There is no such thing as "de_DE.cp1252" locale that works with UTF8
data --- you'd have to use "de_DE.utf8" instead.

You haven't explained exactly why you think you have that requirement,
but I wonder whether you aren't confusing client and server encoding.
There's no problem in having a client that is using WIN1252 encoding
while the server uses UTF8 --- just make sure that the client_encoding
parameter is set correctly for that client.

			regards, tom lane