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 5FCDC5571D for ; Thu, 24 Feb 2005 07:42:02 +0000 (GMT) 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 24991-04 for ; Thu, 24 Feb 2005 07:42:01 +0000 (GMT) Received: from ns1.turtle-entertainment.de (ns1.turtle-entertainment.de [193.41.200.20]) by svr1.postgresql.org (Postfix) with ESMTP id B9E65559BD for ; Thu, 24 Feb 2005 07:41:59 +0000 (GMT) Received: from ip96.85.1311c-cud12k-02.ish.de ([62.143.85.96] helo=mail.office.turtle-entertainment.de) by ns1.turtle-entertainment.de with asmtp (Exim 3.22 #3 (Debian)) id 1D4DdF-0008TP-00; Thu, 24 Feb 2005 08:41:57 +0100 Received: from ip19.1.1411j-cud12k-02.ish.de ([62.143.1.19] helo=[192.168.100.5]) by mail.office.turtle-entertainment.de with asmtp (Exim 3.22 #7 (Debian)) id 1D4DdF-0002xf-00; Thu, 24 Feb 2005 08:41:57 +0100 Message-ID: <421D8541.2000904@turtle-entertainment.de> Date: Thu, 24 Feb 2005 08:41:53 +0100 From: Bjoern Metzdorf User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: "Pgsql-Admin (E-mail)" Subject: Re: invalid multibyte character for locale References: <421CF15C.6010306@turtle-entertainment.de> <421CF1CE.3000800@turtle-entertainment.de> <23514.1109203127@sss.pgh.pa.us> In-Reply-To: <23514.1109203127@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.851 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL X-Spam-Level: * X-Archive-Number: 200502/277 X-Sequence-Number: 16445 Tom Lane wrote: > Well, in that case your encoding is indeed at variance with your locale > setting ;-). Perhaps you should declare the encoding as SQL_ASCII. > The immediate problem is that mbstowcs() is being called and it > evidently doesn't know what to do in C locale. SQL_ASCII (or any > single-byte encoding) would bypass this code path and avoid the > error. The problem is that we need UNICODE encoding in our database. We make heavy use of UTF-8 (our website is multilingual). I now tried with locale set to de_DE.UTF-8, but CREATE INDEX foobar_uvalue_key ON foobar USING btree (upper((value)::text)); still gives me ERROR: invalid multibyte character for locale. With 7.3 and 7.4 this is working fine. May I assume that 7.3 and 7.4 behaviour is buggy? Is 8.0 just stricter or is this just a side effect of your fix for multibyte upper/lower problem for locale != C? If 7.3 and 7.4 behaviour is intended, is there a way to let 8.0 behave the same? Regards, Bjoern