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

From Tom Lane
Subject Re: [HACKERS] Re: pgsql: setlocale() on Windows doesn't work correctly if the locale name
Date
Msg-id 12814.1303258943@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: setlocale() on Windows doesn't work correctly if the locale name  (Hiroshi Inoue <inoue@tpf.co.jp>)
Responses Re: [HACKERS] Re: pgsql: setlocale() on Windows doesn't work correctly if the locale name  (Hiroshi Inoue <inoue@tpf.co.jp>)
List pgsql-committers
Hiroshi Inoue <inoue@tpf.co.jp> writes:
> (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().

Huh?  Bootstrap mode just deals with the data found in
src/include/catalog/*.h.  The locale names found by initdb.c are stuck
in there afterwards, using regular SQL commands.  I don't know where the
problem really comes from, but I doubt the connection you're trying to
make above.

            regards, tom lane

pgsql-committers by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: pgsql: setlocale() on Windows doesn't work correctly if the locale name
Next
From: Bruce Momjian
Date:
Subject: pgsql: Throw error for mismatched pg_upgrade clusters