From: Kris Kiger <kris@musicrebellion.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Juan Miguel <juanmime@ono.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Speed & Memory Management
Date: Thu, 03 Apr 2003 14:26:36 -0500
Message-ID: <3E8C8AEC.607@musicrebellion.com> (raw)
References: <Pine.LNX.4.44.0304030018580.3656-100000@peter.localdomain>
Under what circumstances does a character not take up a set number of
bytes? For example, i was under the impression that utf-8 allocated 6
bytes per character. While the character may not occupy all six bytes,
each byte would still be reserved for that character set.
Kris
>Juan Miguel writes:
>
>
>
>>Well ... but ... reading database theory books, you can see that fixed size
>>records are "better" than variant size records.
>>
>>
>
>Theory and practice are only the same in theory. In practice there is a
>difference.
>
>Anyway, char(30) means 30 characters, not 30 bytes. So it's not a
>fixed-size record anyway. Other factors are out-of-line storage and
>automatic compression of long values.
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: kris@musicrebellion.com, peter_e@gmx.net, juanmime@ono.com
Subject: Re: Speed & Memory Management
In-Reply-To: <3E8C8AEC.607@musicrebellion.com>
References: <Pine.LNX.4.44.0304030018580.3656-100000@peter.localdomain> <3E8C8AEC.607@musicrebellion.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox