2010/1/21 Heikki Linnakangas
> The login screen says:
>
> Windows Server 2003 R2, Datacenter x64 Edition
>
> > What version of Postgres you have used? Is it 8.3.3 or 8.4.2 like mine?
>
> A fresh checkout from CVS HEAD.
>
> > What encoding/collation was your DB created with? Was it UTF8 /
> > 'Pol
2010/1/20 Heikki Linnakangas
>
> I happen to have access to a Win32 virtual machine just now. CVS HEAD,
> built from sources on the VM.
>
> Seems to work fine. The test case runs for ages, I'm at about 1/3
> through it, and no errors this far. I'm going to have to kill it now.
>
> --
> Heikki Li
2010/1/20 Tom Lane
>
> I tried the test case on Linux (Fedora 11) with locale pl_PL.utf8,
> and unsurprisingly failed to reproduce the problem. So it's something
> specific to Windows. Can anyone else reproduce it?
>
>regards, tom lane
>
If it is of any help: changing
2010/1/19 Tom Lane
>
> What that sounds like is a locale/encoding conflict. Postgres depends
> on strcoll() or local equivalent to produce consistent sort results,
> and sometimes if strcoll is presented with data that it thinks is
> invalidly encoded, it doesn't behave sanely.
>
> What locale s
