> No, not particularly. The C language standard is quite clear about > that. Nor does it seem like a particularly great idea from a user's > standpoint for different sub-parts of a program to be operating in > different locales. Even if I agreed with the concept, your idea of > switching locale constantly is likely to be horrid from a performance > standpoint.
I just don't known way the default locale is "C" but not the value Set by Environment Variables in Linux. Maybe this is The C language standard. And may be this is a general knowledge known by most of people except for a few (just like me ). If someone does not know that,it's not too easy to solve it by him self. Whether it's better to do something to make using native language of libpq more easy? Even if write something in document. By the way, from a performance standpoint normally native language only needed for error message outputing where I think performance is not so important. Regards chen huajun -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
