Re: Adding German Character Set to PostgresSQL - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Adding German Character Set to PostgresSQL
Date
Msg-id 201201021358.59590.adrian.klaver@gmail.com
Whole thread Raw
In response to Re: Adding German Character Set to PostgresSQL  ("Hagen Finley" <finhagen@comcast.net>)
Responses Re: Adding German Character Set to PostgresSQL  ("Hagen Finley" <finhagen@comcast.net>)
List pgsql-general
On Monday, January 02, 2012 1:47:13 pm Hagen Finley wrote:
> Hannes,
>
> The output of \l is:
>
> gpdemo=# \l
>                    List of databases
>     Name    |  Owner  | Encoding |  Access privileges
> ------------+---------+----------+---------------------
>  acn                | gpadmin | UTF8     |
>  gpdemo      | gpadmin | UTF8     |
>  philosophy | gpadmin | UTF8     |
>  postgres     | gpadmin | UTF8     |
>  template0  | gpadmin | UTF8     | =c/gpadmin  : gpadmin=CTc/gpadmin
>  template1  | gpadmin | UTF8     | =c/gpadmin   : gpadmin=CTc/gpadmin
>
> It would be easy enough to create a new database with a different encoding
> - only one record in the one in question. However, it sounded as though
> you don't believe that is the issue - that UTF8 ought to support the
> German characters I want. Am I understanding you correctly?

So now we have established where it is going to. Now to find out where it is
coming from. You said the server is running on Centos and that it was presumably
set up for a German keyboard.
From a terminal in Centos what do the below show?
locale
locale -a


>
> Hagen
>

--
Adrian Klaver
adrian.klaver@gmail.com

pgsql-general by date:

Previous
From: "Hagen Finley"
Date:
Subject: Re: Adding German Character Set to PostgresSQL
Next
From: David Johnston
Date:
Subject: Re: Verifying a timestamp is null or in the past