| From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: encoding of PostgreSQL messages |
| Date: | 2009-01-30 15:11:05 |
| Message-ID: | 49831889.2020103@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
This topic seems to be related to the bug report
[ODBC] Localized error messages, wrong charset
.
Bruce Momjian wrote:
> Added to TODO:
>
> Improve encoding of connection startup messages sent to the client
>
> Currently some authentication error messages are sent in the server
> encoding
It it true ?
IIRC the backend knows nothing about the server encoding in
authentication phase.
Psqlodbc Unicode driver sends connection startup message which
contains the client_encoding(=UTF8) guc parameter. Attached is
a trial patch so that the psqlodbc Unicode driver can get
properly localized password error messages.
regards,
Hiroshi Inoue
| Attachment | Content-Type | Size |
|---|---|---|
| processStartup.diff | text/plain | 735 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Asko Oja | 2009-01-30 15:32:17 | Re: database/table snapshot |
| Previous Message | A B | 2009-01-30 15:05:58 | Re: Runaway postgres process? |