Re: initdb.exe changes --locale option - Mailing list pgsql-bugs

From Tom Lane
Subject Re: initdb.exe changes --locale option
Date
Msg-id 12506.1347631787@sss.pgh.pa.us
Whole thread Raw
In response to Re: initdb.exe changes --locale option  (Dave Page <dpage@pgadmin.org>)
Responses Re: initdb.exe changes --locale option  (Dave Page <dpage@pgadmin.org>)
List pgsql-bugs
Dave Page <dpage@pgadmin.org> writes:
> On Fri, Sep 14, 2012 at 6:14 AM, Sandeep Thakkar
> <sandeep.thakkar@enterprisedb.com> wrote:
>> No.. what I mean to say is that the output from getlocales is same in 9.1
>> and 9.2.  (I checked the installation logs). It's initdb in 9.2 that is not
>> accepting the same output. So, it has nothing to with the VC++ runtimes.

> Ah, OK. Sorry - misunderstood what you were saying. I guess it could
> still be the runtimes, but affecting initdb, though a quick look at
> the initdb commit logs shows this
> http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=a88b6e4cfbff9802906dd400ef334ffa49e7f286,
> which I'd immediately suspect as at least part of the culprit, except
> that it was apparently backported to 9.1.

Actually, 9.2 intentionally tries to canonicalize locale names, see
commit c7cea267de3ca05b29a57b9d113b95ef3793c8d8.  Microsoft's support
of setlocale seems to be shoddy enough that it wouldn't be surprising
if there were some issue there.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: Re: Probable bug with CreateFakeRelcacheEntry (now with reproducible test case)
Next
From: Tom Lane
Date:
Subject: Re: BUG #7516: PL/Perl crash