| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | david(at)kineticode(dot)com |
| Cc: | barwick(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org, twanger(at)bluetwanger(dot)de |
| Subject: | Re: UTF-8 and LIKE vs = |
| Date: | 2004-08-24 14:52:23 |
| Message-ID: | 20040824.235223.74749949.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > Locales for multibyte encodings are often broken on many platforms. I
> > see identical things with Japanese on Red Hat. This is one of the
> > reason why I tell Japanese PostgreSQL users not to enable locale while
> > initdb...
>
> Yep, and exporting my data, deleting the data directory, running initdb
> with --locale=C fixd the problem for me. Woot!
>
> But given what you've said, Tatsuo, it makes me wonder if it's worth it
> to use the system locale default when running initdb? Maybe it'd make
> more sense for PostgreSQL to default to C unless someone specifies
> another --locale?
You are quite right. initdb defaults to use the system locale is
evil. I have been saying this for long time...
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Amiel | 2004-08-24 14:56:54 | pg_stat_activity versus ps |
| Previous Message | mike | 2004-08-24 14:42:53 | Invalid input for integer on VIEW |