Re: Locale / Encoding mismatch

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Naz Gassiep <naz(at)mira(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Locale / Encoding mismatch
Date: 2008-03-30 18:03:58
Message-ID: 47EFD60E.2030406@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

PG 8.3 has strict rule what CTYPE and LOCALLE is allowed. It is protection
before possible problems with data processing. You probably need set en_AU.uft8
locale when you initialize server.

Zdenek

Naz Gassiep napsal(a):
> I have just attempted to upgrade to 8.3.1 and I now get this error when
> trying to create a UTF8 DB:
>
> postgres(at)mrnaz:~$ createdb twerl -E utf8
> createdb: database creation failed: ERROR: encoding UTF8 does not match
> server's locale en_AU
> DETAIL: The server's LC_CTYPE setting requires encoding LATIN1.
>
> I have never bothered with the server's locale, all the locale handling
> in the app gets handled within the DB itself. I guess I now have to dig
> into the murky world of system locales and how they affect my app
> ecosystem. I don't suppose there is an easy solution to this and a short
> explanation of why it now occurs is there?
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2008-03-30 18:04:47 Re: Using tables in other PostGreSQL database
Previous Message Martijn van Oosterhout 2008-03-30 18:01:58 Re: Locale / Encoding mismatch