From: "Peter Eisentraut" <pete...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
