From: | Andrew - Supernews <andrew+nonews(at)supernews(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Reducing the overhead of NUMERIC data |
Date: | 2005-11-03 19:41:18 |
Message-ID: | slrndmkpuu.g61.andrew+nonews@trinity.supernews.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On 2005-11-03, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
>> For "other databases", the column could be encoded as 2 byte characters
>> or 4 byte characters, allowing it to be fixed. I find myself doubting
>> that ASCII characters could be encoded more efficiently in such formats,
>> than the inclusion of a length header and per character length encoding,
>> but for multibyte characters, the race is probably even. :-)
>
> That's called UTF-16 and is currently not supported by PostgreSQL at
> all. That may change, since the locale library ICU requires UTF-16 for
> everything.
Even UTF-16 is not fixed-length; some characters require 4 bytes, not 2.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-11-03 20:12:46 | Re: Reducing the overhead of NUMERIC data |
Previous Message | Andrew - Supernews | 2005-11-03 19:40:15 | Re: Exclusive lock for database rename |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-11-03 20:08:17 | Re: Limit usage of tcop/dest.h |
Previous Message | Merlin Moncure | 2005-11-03 19:31:58 | Re: Limit usage of tcop/dest.h |