| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: encoding of PostgreSQL messages |
| Date: | 2008-12-29 12:07:14 |
| Message-ID: | 20081229120714.GB4545@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Karsten Hilbert wrote:
> On Tue, Dec 23, 2008 at 06:45:17PM -0300, Alvaro Herrera wrote:
> > Hmm, isn't client_encoding reported in the startup packet sent by the
> > server, after auth?
>
> That would not quite be enough -- I am talking about
> messages reported *during* auth, say
>
> FATAL: password authentication failed for user "postgres"
>
> or
>
> fe_sendauth: no password supplied
>
> both of which, in other locales, may contain non-ASCII characters.
Those are sent in the server encoding IIRC (which admittedly you don't
have a way to know, at that point.)
And I'm now wondering if we should delay initializing the translation
stuff until after client_encoding has been reported.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2008-12-29 12:22:58 | Re: open transaction? |
| Previous Message | Raymond O'Donnell | 2008-12-29 12:06:04 | Re: open transaction? |