Re: character encoding in StartupMessage

John DeSoi <desoi@pgedit.com>

From: John DeSoi <desoi@pgedit.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>, PG Hackers <pgsql-hackers@postgresql.org>
Date: 2006-02-28T15:14:51Z
Lists: 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