Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 5A627632E9B for ; Tue, 27 Jul 2010 00:37:01 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 87395-09 for ; Tue, 27 Jul 2010 03:36:54 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id 7DA37632A0D for ; Tue, 27 Jul 2010 00:36:54 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id 177D536438F; Mon, 26 Jul 2010 20:36:48 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QaRpxRVE6muc; Mon, 26 Jul 2010 20:36:45 -0700 (PDT) Received: from alvh.no-ip.org (unknown [186.9.141.120]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id 4F14236438E; Mon, 26 Jul 2010 20:36:43 -0700 (PDT) Received: by alvh.no-ip.org (Postfix, from userid 1000) id C7B07438210; Mon, 26 Jul 2010 23:36:33 -0400 (CLT) Content-Type: text/plain; charset=UTF-8 Cc: Benjamin Krajmalnik , pgsql-admin Subject: Re: upper and UTF-8 From: Alvaro Herrera To: Scott Marlowe In-reply-to: References: <1280196392-sup-6027@alvh.no-ip.org> Date: Mon, 26 Jul 2010 23:36:33 -0400 Message-Id: <1280201350-sup-1392@alvh.no-ip.org> User-Agent: Sup/git Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.001 tagged_above=-10 required=5 tests=BAYES_20=-0.001 X-Spam-Level: X-Archive-Number: 201007/186 X-Sequence-Number: 35205 Excerpts from Scott Marlowe's message of lun jul 26 23:12:08 -0400 2010: > On Mon, Jul 26, 2010 at 8:09 PM, Alvaro Herrera > wrote: > > I suspect that the problem is an incorrect client_encoding setting. > > Yeah, OP had set lc_collate to C under the mistaken impression that > collation controlled the character sets you could insert into the > database. If you create a db with lc_collate='C' then the upper only > works on basic ascii characters near as I can tell. Makes sense. The code seems to say that it's lc_ctype that's important though, see str_toupper in formatting.c. So I think you could still set collation to C and use a language-specific lc_ctype.