Alvaro Herrera <[EMAIL PROTECTED]> writes: > Ideally, it should be an error to set lc_messages to a value that's not > compatible with the current encoding. Do we do that currently elsewhere?
We don't currently enforce that, and I'm not sure it's possible to do so on non-Windows machines. AFAIR the POSIX API doesn't even associate a character set with anything but LC_CTYPE. Does it make any sense to wire in the assumption that locale names have the form "something.encoding-id"? If we did that, we could enforce that the encoding-id part matches LC_CTYPE, or maybe even just alter the presented values for other LC_foo variables to match. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings