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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: ivocs admin <gh0st(at)ivocs(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Locale (unsupported) bug. uk_UA.KOI8-U
Date: 2008-10-09 16:09:10
Message-ID: 48EE2CA6.3030106@gmx.net (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> ivocs admin wrote:
>>> 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/
> 
> It's still not going to find a suitable text search configuration,
> since we haven't got anything for Ukranian ...

But initdb will still succeed, so if you don't need the text search 
feature, you can proceed.  If you do need text search, you can possibly 
get away with using the configuration for russian (see initdb -T 
option).  Do let us know if we need to make any adjustments to support 
Ukrainian better.

In response to

pgsql-bugs by date

Next:From: zhengzhong_zhouDate: 2008-10-10 07:59:21
Subject: BUG #4463: unique constraint error
Previous:From: Tom LaneDate: 2008-10-09 15:55:10
Subject: Re: BUG #4462: Adding COUNT to query causes massive slowdown

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