On 8/4/16 2:45 AM, Victor Wagner wrote:
> 4. At the session startup try to reinitializie LC_MESSAGES locale
> category with the combination
> of the server (or better client-send) language and region and
> client-supplied encoding, and if this failed, use untranslated error
> message. Obvoisly, attempt to set locale to ru_RU.ISO8859-1 would fail.
> so, if client would ask server with ru_RU.UTF-8 default locale to use
> LATIN1 encoding, server would fallback to untranslated messages.
I think this is basically my solution (1), with the same problems.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
