Message-ID: <42357AA0.4090303@t1.unisoftbg.com>
Date: Mon, 14 Mar 2005 12:50:56 +0100
From: pginfo <pginfo@t1.unisoftbg.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.0.1) Gecko/20020823 Netscape/7.0
MIME-Version: 1.0
To: =?windows-1252?Q?Miroslav_=8Aulc?= <miroslav.sulc@startnet.cz>
Cc: pgsql-sql@postgresql.org
Subject: Re: lower and unicode
References: <423528B6.2070407@t1.unisoftbg.com> <42354812.7030106@startnet.cz>
	<42355BFC.4080409@t1.unisoftbg.com> <42356AB5.1010306@startnet.cz>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Hi,
I am using --no-locale by init db.
I readet that if I am using some locale the pg will work very slow.
Have you noticed some speed penalty by using cs_CZ.utf8.
regards,
ivan.

Miroslav Šulc wrote:

> pginfo wrote:
>
>> Hi,
>> I am uusing pg 8.0.1 on FreeBSD 5.3 but I am ready t use the version 
>> taht supports correct unicode.
>
>
> I think that should be fine. I use PostgreSQL 8.0.1 on Linux (Gentoo) 
> without these problems (I used cs_CZ.utf8 to init my db). What you 
> write seems to me that you have your database initialized to something 
> else than xy_XY.utf8 which must be used to have databases working 
> correctly with UNICODE. Try 'locale -a' and choose your locale that 
> has *.utf8 to initialize the database. Then things should be O.K. :-)
>
> I don't remember I've seen some note in documentation that users must 
> use for databases the same encoding as they used for initdb. If this 
> is true, it would be time saving to mention this in documentation (if 
> it is not already there).
>
>>
>> regards,
>> ivan.
>
>
> Miroslav