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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: UTF-8 and LIKE vs =


  • From: David Wheeler <david@kineticode.com>
  • To: Tatsuo Ishii <t-ishii@sra.co.jp>
  • Cc: barwick@gmail.com, pgsql-general@postgresql.org, twanger@bluetwanger.de
  • Subject: Re: UTF-8 and LIKE vs =
  • Date: Mon, 23 Aug 2004 17:53:03 -0700
  • Message-id: <F47BE1C2-F567-11D8-990D-000A95972D84@kineticode.com>

On Aug 23, 2004, at 5:22 PM, Tatsuo Ishii wrote:

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?

Thanks for the help, everyone,

David

Attachment: smime.p7s
Description: S/MIME cryptographic signature



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group