Skip site navigation (1) Skip section navigation (2)

Re: Locale (unsupported) bug. uk_UA.KOI8-U

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: ivocs admin <gh0st(at)ivocs(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Locale (unsupported) bug. uk_UA.KOI8-U
Date: 2008-10-09 12:01:37
Message-ID: 48EDF2A1.8080801@gmx.net (view raw or flat)
Thread:
Lists: pgsql-bugs
ivocs admin wrote:
> initdb -E ISO-8859-1 -D data/

This is probably not a good idea.  You should specify a locale and let 
initdb figure out the matching encoding.  Otherwise you might end up 
with an incompatible locale/encoding combination.  (initdb would 
probably not even allow this to proceed, but you have other problems as 
well, see below.)

> The files belonging to this database system will be owned by user 
> "postgres".
> This user must also own the server process.
> 
> The database cluster will be initialized with locale uk_UA.KOI8-U.
> could not determine encoding for locale "uk_UA.KOI8-U": codeset is "KOI8-U"
> initdb: could not find suitable text search configuration for locale 
> uk_UA.KOI8-U

PostgreSQL currently doesn't support the KOI8-U encoding.  You could 
consider using UTF-8 instead.  Try running this

initdb --locale=uk_UA.utf8 -D data/


In response to

Responses

pgsql-bugs by date

Next:From: Peter EisentrautDate: 2008-10-09 12:05:10
Subject: Re: BUG #4462: Adding COUNT to query causes massive slowdown
Previous:From: ivocs adminDate: 2008-10-09 09:37:00
Subject: Locale (unsupported) bug. uk_UA.KOI8-U

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group