Magnus Hagander wrote:
> Do you know enough to say exactly which locale/encoding
> combinations have to be removed fromt he installer?
The encodings are:
LATIN6 (ISO 8859-10/ECMA 144)
LATIN7 (ISO 8859-13)
LATIN8 (ISO 8859-14)
LATIN10 (ISO 8859-16/ASRO SR 14111
While you can still create databases using these encodings, it's not
possible to initb with a locale that uses the same encoding. This means
ORDER BY, UPPER() and similar will produce wrong results.
I guess I'll resubmit my installer patch for listing locales supported
by the system, this time without the encodings listed above. That way
most users won't see unsupported encodings, while people who know what
they're doing can still reach them by using CREATE DATABASE newdb
>>Last October there was a discussion on pgsql-hackers about
>>writing locale support for PG, so it wouldn't depend on the
>>system for locale functionality any more. Is anyone still
>>working on that?
> I have no idea, but I'm certain if someone is this is definitly not
> going to happen for 8.0.
I know this feature can't make it into 8.0; but blaming Windows for more
than one release cycle might not look very good. :-(
In response to
pgsql-hackers-win32 by date
|Next:||From: Rob McCarthy||Date: 2004-11-17 16:11:07|
|Subject: Initdb Fail installing PostgreSQL 8.0.0 Beta 4|
|Previous:||From: Bruce Momjian||Date: 2004-11-11 15:05:22|
|Subject: Re: locales and encodings on Windows|