Skip site navigation (1) Skip section navigation (2)

Re: character encoding in StartupMessage

From: John DeSoi <desoi(at)pgedit(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: character encoding in StartupMessage
Date: 2006-02-28 15:14:51
Message-ID: 00081276-7339-47F3-85E0-49D1413D3831@pgedit.com (view raw or flat)
Thread:
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


In response to

pgsql-hackers by date

Next:From: Jonah H. HarrisDate: 2006-02-28 15:26:05
Subject: Re: bug in 7.3.2
Previous:From: Alvaro HerreraDate: 2006-02-28 15:05:17
Subject: Re: character encoding in StartupMessage

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group