Peter Eisentraut <peter@eisentraut.org> writes:
> I'm not sure what to do with this. If setlocale() and newlocale()
> indeed behave differently in what set of locale names they accept, then
> technically we ought to test both of them, since we do use both of them
> later on. Or maybe we push on with the effort to get rid of setlocale()
> calls and then just worry about testing newlocale() (as this patch
> does). But right now, if newlocale() is more permissive, then we could
> accept locale names that will later fail setlocale() calls, which might
> be a problem.
I think the clear answer is "let's stop using setlocale(), and then
not have to worry about any behavioral differences".
regards, tom lane
