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
> 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
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
pgsql-bugs by date
|Next:||From: Peter Eisentraut||Date: 2008-10-09 12:05:10|
|Subject: Re: BUG #4462: Adding COUNT to query causes massive slowdown|
|Previous:||From: ivocs admin||Date: 2008-10-09 09:37:00|
|Subject: Locale (unsupported) bug. uk_UA.KOI8-U|