"Hiroshi Saito" <[EMAIL PROTECTED]> wrote:

> Ah Ok, Please check it.

Your patch looks useful to prevent mismatch of encoding and locale on Windows,
but I found there is a limitation that user will not able to specify locale.
I added an alternative of nl_langinfo(CODESET) for Win32.

Please check following commands:
 initdb --encoding=EUC_jp --locale=Japanese_Japan.932
 initdb --encoding=EUC_jp --locale=Japanese_Japan.20932

One problem is that user need to know codepage numbers. It might
be possible to replace the default codepage to server encodings
automatically if we have a mapping table from encoding to codepage.

ITAGAKI Takahiro
NTT Open Source Software Center

Attachment: chklocale-v2.patch
Description: Binary data

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to