> Come on, people. This was the second time I reported this bug
> and also the second time nobody responded to my report. :-(
'fraid I know very little about this stuff, so I can't really comment on
the mani issue.. Was hoping someone else would pick it up...
> If it is indeed not possible to initdb with a utf8 (65001)
> locale, then this will cause a flood of bug reports once a
> large number of people start using PG on Windows. Can
> somebody try and confirm this problem?
> Simply try running initdb with a --locale value of
> german_germany.65001, spanish_spain.65001,
> french_france.65001 or any other locale you think should be
> supported by your system. You will need to do this from the
> command line, not from the installer. Does initdb accept this
> value or does it replace it with your current system locale?
>
> Unless somebody can come up with a solution, my suggestion
> for a work-around would be to remove unsupported encodings
> from the installer or at least warn users that their database
> will not be fully functional if they happen to choose one of
> the unsupported encodings.
Yeah, that sounds like what we'll have to do if nobody can fix this
completely. Do you know enough to say exactly which locale/encoding
combinations have to be removed fromt he installer?
Bruce - we probably need an open item on the backend side of this. If
not, then we need at least someone to say we can't fix this for 8.0.
Removing it from the installer is just a workaround...
> Last October there was a discussion on pgsql-hackers about
> writing locale support for PG, so it wouldn't depend on the
> system for locale functionality any more. Is anyone still
> working on that?
I have no idea, but I'm certain if someone is this is definitly not
going to happen for 8.0.
//Magnus
