> > 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...
In response to
pgsql-general by date
|Next:||From: Jeff Amiel||Date: 2004-08-24 14:56:54|
|Subject: pg_stat_activity versus ps|
|Previous:||From: mike||Date: 2004-08-24 14:42:53|
|Subject: Invalid input for integer on VIEW|