Skip site navigation (1) Skip section navigation (2)

Re: invalid multibyte character for locale

From: Bjoern Metzdorf <bm(at)turtle-entertainment(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Pgsql-Admin (E-mail)" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: invalid multibyte character for locale
Date: 2005-02-24 07:41:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-adminpgsql-hackerspgsql-patches
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?


In response to


pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2005-02-24 09:29:15
Subject: Re: Finding if old transactions are running...
Previous:From: Christopher BrowneDate: 2005-02-24 05:32:36
Subject: Re: Finding if old transactions are running...

pgsql-admin by date

Next:From: Alex GutmanDate: 2005-02-24 13:33:08
Subject: Preventing changes to default settings of a collective account?
Previous:From: EnvbopDate: 2005-02-24 05:18:01
Subject: Newbie - Pointers on moving.

pgsql-patches by date

Next:From: Ron MayerDate: 2005-02-24 08:49:36
Subject: Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.
Previous:From: Tom LaneDate: 2005-02-24 01:36:07
Subject: Re: [PATCHES] [pgsql-hackers-win32] Repleacement for src/port/snprintf.c

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group