Re: Reducing the overhead of NUMERIC data - Mailing list pgsql-hackers

From Andrew - Supernews
Subject Re: Reducing the overhead of NUMERIC data
Date
Msg-id slrndmkpuu.g61.andrew+nonews@trinity.supernews.net
Whole thread Raw
In response to Re: Reducing the overhead of NUMERIC data  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On 2005-11-03, Martijn van Oosterhout <kleptog@svana.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


pgsql-hackers by date:

Previous
From: Andrew - Supernews
Date:
Subject: Re: Exclusive lock for database rename
Next
From: Simon Riggs
Date:
Subject: Re: Reducing the overhead of NUMERIC data