On Tue, 25 Nov 2003, Tatsuo Ishii wrote:
> I'm tired of telling that Unicode is not that perfect. Another gottcha
> with Unicode is the UTF-8 encoding (currently we use) consumes 3
> bytes for each Kanji character, while other encodings consume only 2
> bytes. IMO 3/2 storage ratio could not be neglected for database use.
I'm aware of how utf-8 works and I was talking about the message
cataloges. It does not affect what you store in the database in any way.
--
/Dennis
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
