Hiroshi Inoue <in...@tpf.co.jp> writes: > I see another issue for the behavior.
> For example, the following code in src/backend/utis/adt/pg_locale.c > won't work as expected in case the current locale is Hong Kong, Macao or > UAE because the last setlocale() in the code would fail. I can > find such save & restore operations of locales in several places. Well, if Windows' setlocale is too brain-dead to accept its own output, there's nothing to be done about it except to file a bug with Microsoft. There isn't anything in the POSIX API that would let us avoid using setlocale with a previous result value to restore the previous setting. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers