mha@postgresql.org (Magnus Hagander) writes:
> Re-allow UTF8 encodings on win32. Since UTF8 is converted to
> UTF16 before being used, all (valid) locales will work for this.

So where do we stand on the Windows locale/encoding business --- are
we happy with the behavior now, or does it still need work?

regards, tom lane

---------------------------(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
match

Tom Lane wrote:
> mha@postgresql.org (Magnus Hagander) writes:
>> Re-allow UTF8 encodings on win32. Since UTF8 is converted to
>> UTF16 before being used, all (valid) locales will work for this.
>
> So where do we stand on the Windows locale/encoding business --- are
> we happy with the behavior now, or does it still need work?

I think we're good. But I'd like to hear some verification from somebody
else. Specifically, I'd like to hear a signoff from someone who can
actually do "real tests" on a locale that's not US and not Swedish.
Also, I'd like to hear from the Japanese people (Hiroshi? Can you do
this?) that we didn't break it for them. I don't think we did, but I
want to be sure

Hiroshi, and whomever else can help to test, this is only testing the
backend, not the installer. The installer may need a few minor tweaks
still once the backend is considered fixed. And what needs to be tested
is CVS HEAD as of today.

//Magnus

---------------------------(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
match

Hi.

Um, It seems that it only passed the strict check of chklocale.c. Probably, It may
enable mistaken selection...However, I will clarify a problem by the test.

Regards,
Hiroshi Saito

From: "Magnus Hagander" <magnus@hagander.net>


> Tom Lane wrote:
>> mha@postgresql.org (Magnus Hagander) writes:
>>> Re-allow UTF8 encodings on win32. Since UTF8 is converted to
>>> UTF16 before being used, all (valid) locales will work for this.
>>
>> So where do we stand on the Windows locale/encoding business --- are
>> we happy with the behavior now, or does it still need work?
>
> I think we're good. But I'd like to hear some verification from somebody
> else. Specifically, I'd like to hear a signoff from someone who can
> actually do "real tests" on a locale that's not US and not Swedish.
> Also, I'd like to hear from the Japanese people (Hiroshi? Can you do
> this?) that we didn't break it for them. I don't think we did, but I
> want to be sure
>
> Hiroshi, and whomever else can help to test, this is only testing the
> backend, not the installer. The installer may need a few minor tweaks
> still once the backend is considered fixed. And what needs to be tested
> is CVS HEAD as of today.
>
> //Magnus

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

2007/10/16, Magnus Hagander <magnus@hagander.net>:
> Tom Lane wrote:
> > mha@postgresql.org (Magnus Hagander) writes:
> >> Re-allow UTF8 encodings on win32. Since UTF8 is converted to
> >> UTF16 before being used, all (valid) locales will work for this.
> >
> > So where do we stand on the Windows locale/encoding business --- are
> > we happy with the behavior now, or does it still need work?
>
> I think we're good. But I'd like to hear some verification from somebody
> else. Specifically, I'd like to hear a signoff from someone who can
> actually do "real tests" on a locale that's not US and not Swedish.
> Also, I'd like to hear from the Japanese people (Hiroshi? Can you do
> this?) that we didn't break it for them. I don't think we did, but I
> want to be sure
>
> Hiroshi, and whomever else can help to test, this is only testing the
> backend, not the installer. The installer may need a few minor tweaks
> still once the backend is considered fixed. And what needs to be tested
> is CVS HEAD as of today.
>
> //Magnus
>
> ---------------------------(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
> match
>

I can test it with czech locale. Can I download binaries anywhere?

Pavel

---------------------------(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
match

Hi.

> I can test it with czech locale. Can I download binaries anywhere?
http://winpg.jp/~saito/pg83/postgresql-8.3beta-cvs.tgz
It is a thing after regression test.(MinGW+gcc)

Regards,
Hiroshi Saito

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Hi.

> Um, It seems that it only passed the strict check of chklocale.c. Probably, It may
> enable mistaken selection...However, I will clarify a problem by the test.

First, it is one problem....
http://winpg.jp/~saito/pg83/pg83b1-err.txt

And a test continues....

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Hi.

Second, it is big problem....
http://winpg.jp/~saito/pg83/pg83b1-err2.txt
It is text serch config error.
However, It passes initdb.(locale=Japanese_Japan.932 ... This is ShiftJIS locale)

And a test continues....

Regards,
Hiroshi Saito

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Hiroshi Saito wrote:
> Hi.
>
>> Um, It seems that it only passed the strict check of chklocale.c.
>> Probably, It may enable mistaken selection...However, I will clarify a
>> problem by the test.
>
> First, it is one problem....
> http://winpg.jp/~saito/pg83/pg83b1-err.txt
>
> And a test continues....

But SJIS isn't supposed to work, no?

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Hiroshi Saito wrote:
> Hi.
>
> Second, it is big problem....
> http://winpg.jp/~saito/pg83/pg83b1-err2.txt
> It is text serch config error.
> However, It passes initdb.(locale=Japanese_Japan.932 ... This is
> ShiftJIS locale)
>
> And a test continues....

What text search config would you expect?

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Hi.

> Hiroshi Saito wrote:
>> Hi.
>>
>> Second, it is big problem....
>> http://winpg.jp/~saito/pg83/pg83b1-err2.txt
>> It is text serch config error.
>> However, It passes initdb.(locale=Japanese_Japan.932 ... This is
>> ShiftJIS locale)
>>
>> And a test continues....
>
> What text search config would you expect?

This problem here is that locale of initdb passes Japanese_Japan.932.

Regards,
Hiroshi Saito

---------------------------(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
match