"Magnus Hagander" <mha(at)sollentuna(dot)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
In response to
pgsql-hackers-win32 by date
|Next:||From: Roland Volkmann||Date: 2004-12-31 20:26:43|
|Subject: Re: UNICODE/UTF-8 on win32|
|Previous:||From: Magnus Hagander||Date: 2004-12-31 15:26:48|
|Subject: UNICODE/UTF-8 on win32|