Encoding of early PG messages

Поиск
Список
Период
Сортировка
От Shay Rojansky
Тема Encoding of early PG messages
Дата
Msg-id CADT4RqA1F1cKWONw_BvX8LEtcO5BioU8+Q+j+=NaK_ORTWQepw@mail.gmail.com
обсуждение исходный текст
Ответы Re: Encoding of early PG messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Дерево обсуждения
Hi hackers.

Developing Npgsql I've encountered the problem described in http://www.postgresql.org/message-id/20081223212414.GD3894@merkur.hilbert.loc: a German installation of PostgreSQL seems to respond to an incorrect password with a non-UTF8 encoding of the error messages, even if the startup message contains client_encoding=UTF8.

It seems that the aforementioned thread didn't lead to a fix (either to respect client_encoding even for early messages, or to switch to ASCII English errors for these messages). Am I missing something here or is this the current situation in PG? Any plans for some sort of fix?

I can work around this by using "relaxed" decoding (i.e. not failing on non-UTF8 characters) but this means that error messages are partially or totally garbled...

Thanks,

Shay

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Doubt about AccessExclusiveLock in ALTER TABLE .. SET ( .. );
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: Doubt about AccessExclusiveLock in ALTER TABLE .. SET ( .. );