Re: [COMMITTERS] pgsql: setlocale() on Windows doesn't work correctly if the locale name - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject Re: [COMMITTERS] pgsql: setlocale() on Windows doesn't work correctly if the locale name
Date
Msg-id 4DAE21CE.8030402@tpf.co.jp
Whole thread Raw
Responses Re: Re: [COMMITTERS] pgsql: setlocale() on Windows doesn't work correctly if the locale name
List pgsql-hackers
(2011/04/16 2:56), Heikki Linnakangas wrote:
> setlocale() on Windows doesn't work correctly if the locale name contains
> apostrophes or dots.

As for apostrophes, isn't the cause that initdb loses the single quote
of locale? ([BUGS] BUG #5818: initdb lose the single quote of locale)

As the bug reporter mentions, initdb loses the single quote in reality.
Concretely speaking, scanstr() called from bootscanner.l loses it.
I'm not sure if it's suitable for the bootstrap code to call scanstr().

regards,
Hiroshi Inoue

 > There isn't much hope of Microsoft fixing it any time
> soon, it's been like that for ages, so we better work around it. So, map a
> few common Windows locale names known to cause problems to aliases that work.
>
> Branch
> ------
> master
>
> Details
> -------
> http://git.postgresql.org/pg/commitdiff/d5a7bf8c11c8b66c822bbb1a6c90e1a14425bd6e
>
> Modified Files
> --------------
> src/bin/initdb/initdb.c |   89 +++++++++++++++++++++++++++++++++++++++++++----
> 1 files changed, 82 insertions(+), 7 deletions(-)

pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: pgbench \for or similar loop
Next
From: Robert Haas
Date:
Subject: Re: getting to beta