From: | Harald Fuchs <hf0923x(at)protecting(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Reducing the overhead of NUMERIC data |
Date: | 2005-11-05 15:34:56 |
Message-ID: | 87acgj3y73.fsf@srv.protecting.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
In article <e692861c0511041149n6fe36345oba7c43d1d48bef3d(at)mail(dot)gmail(dot)com>,
Gregory Maxwell <gmaxwell(at)gmail(dot)com> writes:
> On 11/4/05, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
>> Yeah, and while one way of removing that dependance is to use ICU, that
>> library wants everything in UTF-16. So we replace "copying to add NULL
>> to string" with "converting UTF-8 to UTF-16 on each call. Ugh! The
>> argument for UTF-16 is that if you're using a language that doesn't use
>> ASCII at all, UTF-8 gets inefficient pretty quickly.
> Is this really the case? Only unicode values 000800 - 00FFFF are
> smaller in UTF-16 than in UTF-8, and in their case it's three bytes vs
> two. Cyrilic, Arabic, Greek, Latin, etc are all two bytes in both.
IMHO the best encoding for "Cyrilic, Arabic, Greek, Latin, etc" is
ISO-8859-* - just one byte. You need UTF* only when you want to have
more than one of of them in the same column.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2005-11-05 17:34:33 | I can't get row type from tuple (SPI) |
Previous Message | Andrew Dunstan | 2005-11-05 14:46:15 | Re: Old interfaces directory in CVS tree? |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-11-06 08:45:58 | Re: Reducing the overhead of NUMERIC data |
Previous Message | Martijn van Oosterhout | 2005-11-05 10:40:05 | Re: Reducing the overhead of NUMERIC data |