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 6069C55CF9 for ; Thu, 24 Feb 2005 15:15:45 +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 60601-01 for ; Thu, 24 Feb 2005 15:15:42 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 0BAB4555C6 for ; Thu, 24 Feb 2005 15:15:41 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j1OFFo8n024833; Thu, 24 Feb 2005 10:15:51 -0500 (EST) To: Bjoern Metzdorf Cc: "Pgsql-Admin (E-mail)" Subject: Re: invalid multibyte character for locale In-reply-to: <421D8541.2000904@turtle-entertainment.de> References: <421CF15C.6010306@turtle-entertainment.de> <421CF1CE.3000800@turtle-entertainment.de> <23514.1109203127@sss.pgh.pa.us> <421D8541.2000904@turtle-entertainment.de> Comments: In-reply-to Bjoern Metzdorf message dated "Thu, 24 Feb 2005 08:41:53 +0100" Date: Thu, 24 Feb 2005 10:15:50 -0500 Message-ID: <24832.1109258150@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/282 X-Sequence-Number: 16450 Bjoern Metzdorf writes: > Is 8.0 just stricter or is this just a side effect > of your fix for multibyte upper/lower problem for locale != C? Both those statements are true. > If 7.3 and 7.4 behaviour is intended, is there a way to let 8.0 behave > the same? I don't know what behavior you thought you were getting from upper/lower on UTF-8 data in 7.4, but it was surely not correct. If you want to duplicate that misbehavior, try SQL_ASCII with C locale. This does not stop you from storing UTF-8 in your database, mind you --- it just loses validation of encoding sequences and conversion to other schemes. But having said that, upper() should work if the locale matches the encoding. You might take the trouble to trace down exactly what data value it's barfing on. regards, tom lane