UNICODE/UTF-8 does not work on the win32 server. The reason is that
strcoll() and friends don't work with it. To support it on win32, it
needs to be converted to UTF16 and use the wide-character versions of
the fucntion. Which we do not do.
(See
http://archives.postgresql.org/pgsql-hackers-win32/2004-11/msg00036.php
and
http://archives.postgresql.org/pgsql-hackers-win32/2004-12/msg00106.php)
I don't *think* we need to disable ito n the client. AFAIK, the client
interfaces don't use any of these functions, and I've seen reports of
people using that long before we had a native win32 server.
//Magnus
>-----Original Message-----
>From: Tatsuo Ishii [mailto:t-ishii@sra.co.jp]
>Sent: den 1 januari 2005 01:10
>To: tgl@sss.pgh.pa.us
>Cc: Magnus Hagander; pgsql-hackers-win32@postgresql.org
>Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
>
>
>Sorry, but I don't subscribe to pgsql-hackers-win32 list. What's the
>problem here?
>--
>Tatsuo Ishii
>
>> "Magnus Hagander" <mha@sollentuna.net> writes:
>> > We know it's broken and won't be fixed for 8.0.
>>
>> > If we just #ifndef WIN32 the definitions in
>utils/mb/encnames.c it won't
>> > be possible to select that encoding, right? Will that have
>any other
>> > unwanted effects (such as breaking client encodings)? If
>not, I suggest
>> > this is done.
>>
>> I believe the subscripts in those arrays have to match the encoding
>> enum type, so you can't just ifdef out individual entries.
>>
>> > (Or perhaps something can be done in pg_valid_server_encoding?)
>>
>> Making the valid_server_encoding function reject it might work.
>> Tatsuo-san would know for sure.
>>
>> Should we also reject it as a client encoding, or does that work OK?
>>
>> regards, tom lane
>>
>
