Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII

From: "MauMau" <maumau307(at)gmail(dot)com>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII
Date: 2013-09-09 22:11:39
Message-ID: E784F7988ADB4958834F85C046DA94D5@maumau
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
> Does anyone know why the PostgreSQL-supplied part of the error message
> does not get messed up?

That is because bind_textdomain_codeset() is called for postgres.mo in
src/backend/utils/mb/mbutils.c, specifying the database encoding as the
second argument. This is done at session start.

Regards
MauMau

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2013-09-09 22:20:54 memory usage of pg_upgrade
Previous Message David Fetter 2013-09-09 21:56:15 Re: Next CFM?