Postgres Pro
Downloads
Home   >   mailing lists

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

From MauMau
Subject Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII
Date
Msg-id E784F7988ADB4958834F85C046DA94D5@maumau
Whole thread Raw
In response to Re: [bug fix] strerror() returns ??? in a UTF-8/C database with LC_MESSAGES=non-ASCII  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Tree view 
From: "Peter Eisentraut" <peter_e@gmx.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

pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: Next CFM?
Next
From: Jeff Janes
Date:
Subject: memory usage of pg_upgrade