Re: character encoding in StartupMessage - Mailing list pgsql-hackers

From John DeSoi
Subject Re: character encoding in StartupMessage
Date
Msg-id 00081276-7339-47F3-85E0-49D1413D3831@pgedit.com
Whole thread Raw
In response to Re: character encoding in StartupMessage  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Feb 28, 2006, at 1:38 AM, Tom Lane wrote:

>>> I could not find anything in the Frontend/Backend protocol docs  
>>> about
>>> character encoding in the StartupMessage. Assuming it is legal for a
>>> database or user name to have unicode characters, how is this  
>>> handled
>>> when nothing yet has been said about the client encoding?
>
>> A similar badness is that if you issue CREATE DATABASE from a UTF8
>> database, the dbname will be stored as UTF8.  Then, if you go to a
>> LATIN1 database and create another it will be stored as LATIN1.
>
> Yeah, this has been discussed before.  Database and user names both
> have this affliction.

So are the database/user names in the startup message compared using  
the default encoding of the cluster or is just a straight byte  
comparison with no consideration of the encoding?

Thanks,



John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: character encoding in StartupMessage
Next
From: "Jonah H. Harris"
Date:
Subject: Re: bug in 7.3.2