| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | ftm(dot)van(dot)vugt(at)foxi(dot)nl, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: invalid multibyte character for locale |
| Date: | 2005-03-01 01:01:22 |
| Message-ID: | 11380.1109638882@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-patches |
Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> BTW, the current code for upper/lower etc. seems to be broken. The
> exact problem you have are happening in Japanese encodings too(EUC_JP)
> too. PostgreSQL should not use wide-character method if LC_CTYPE is C.
Yeah, we came to that same conclusion a few days ago in another thread.
I am planning to install the fix but didn't get to it yet.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2005-03-01 01:47:23 | Re: pgpool fundamental questions |
| Previous Message | Tom Lane | 2005-03-01 00:59:15 | Re: vacuum_cost_delay & VACUUM holding locks on GIST indexes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank van Vugt | 2005-03-01 12:00:55 | Re: invalid multibyte character for locale |
| Previous Message | Bruce Momjian | 2005-03-01 00:38:39 | Re: Thread-safe snprintf() vsnprintf() and printf() |