Marko Karppinen wrote:
> I think this interaction between the locale and server_encoding is
> confusing. Is there any use case for running an incompatible mix?
> If not, would it not make sense to fetch initdb's default database
> encoding with nl_langinfo(CODESET) instead of using SQL_ASCII?
This would be fine and dandy if we had any sort of idea about what sort
of strings nl_langinfo(CODESET) returns and how to map them to our
encoding names.
