X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8B1AC53CCC for ; Wed, 13 Apr 2005 12:13:51 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 68765-02 for ; Wed, 13 Apr 2005 15:13:48 +0000 (GMT) Received: from mbopi.cytera.com.py (host40-42.wireless.com.py [200.85.40.42]) by svr1.postgresql.org (Postfix) with ESMTP id C099653CA6 for ; Wed, 13 Apr 2005 12:13:45 -0300 (ADT) Received: from [192.168.102.36] (guillermo.cytera.com.py [192.168.102.36]) by mbopi.cytera.com.py (8.12.8/8.12.8) with ESMTP id j3DFAl6R002099 for ; Wed, 13 Apr 2005 11:10:47 -0400 Message-ID: <425D3865.7090406@cybira.biz> Date: Wed, 13 Apr 2005 11:19:01 -0400 From: =?ISO-8859-1?Q?=22Lic=2E_Guillermo_Gonz=E1lez=22?= User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: upper() with LATIN1 problem References: <425BCCC3.40403@cybira.biz> <15653.1113316051@sss.pgh.pa.us> In-Reply-To: <15653.1113316051@sss.pgh.pa.us> X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.401 tagged_above=0 required=5 tests=AWL, BIZ_TLD, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200504/174 X-Sequence-Number: 17187 Hi, I look at the variable/parameter LC_CTYPE and it is set to C (I think this is the default) for performance reason, the installer says. If I use LATIN1 (spanish) what value is the best option for this variable/parameter? Thanks! -- Guillermo González Tom Lane wrote: > =?ISO-8859-1?Q?=22Lic=2E_Guillermo_Gonz=E1lez=22?= writes: > >>The problem is: >>- with a text 'magriñá' >>- the upper('magriñá') returns MAGRIñà >>- NOTE that the characters 'ñ' and 'á' didn't change the case. > > > This is determined by your locale (specifically LC_CTYPE) not by what > the database thinks the encoding is. You'll probably want to re-initdb > in the desired locale. > > regards, tom lane >