Re: String encoding during connection "handshake"

From: sulfinu(at)gmail(dot)com
To: "Trevor Talbot" <quension(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: String encoding during connection "handshake"
Date: 2007-11-28 18:11:00
Message-ID: 200711282011.00419.sulfinu@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday 28 November 2007, Trevor Talbot wrote:
> I'm not entirely sure how that's supposed to solve the client
> authentication issue though. Demanding that clients present auth data
> in UTF-8 is no different than demanding they present it in the
> encoding it was entered in originally...
Oh no, it's a big difference: PREDICTABILITY!
Why must I guess the encoding used by the administrator? What if he's Chinese?
Instead, I know the cluster's encoding, just as I know the server name and
the TCP port. And the connection handshake carries on without
misunderstandings (read wrong encoding).

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-11-28 18:15:52 Re: [HACKERS] Time to update list of contributors
Previous Message Bruce Momjian 2007-11-28 17:58:03 Re: pgindent and multiline string constants