From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bjoern Metzdorf <bm(at)turtle-entertainment(dot)de> |
Cc: | "Pgsql-Admin (E-mail)" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: invalid multibyte character for locale |
Date: | 2005-02-24 15:15:50 |
Message-ID: | 24832.1109258150@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers pgsql-patches |
Bjoern Metzdorf <bm(at)turtle-entertainment(dot)de> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2005-02-24 15:38:00 | Re: Configuration for my server |
Previous Message | Marcin Giedz | 2005-02-24 14:55:58 | Re: Configuration for my server |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-02-24 15:21:16 | Re: [pgsql-hackers-win32] win32 performance - fsync question |
Previous Message | Christopher Kings-Lynne | 2005-02-24 15:02:15 | Re: [pgsql-hackers-win32] win32 performance - fsync question |
From | Date | Subject | |
---|---|---|---|
Next Message | Joel Fradkin | 2005-02-24 16:10:41 | Re: invalid multibyte character for locale |
Previous Message | Simon Riggs | 2005-02-24 13:24:51 | Re: [PATCHES] A way to let Vacuum warn if FSM settings are low. |