Re: [pgsql-performance] Large databases, performance

Shridhar Daithankar <shridhar_daithankar@persistent.co.in>

From: "Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>
To: pgsql-hackers@postgresql.org, pgsql-general <pgsql-general@postgresql.org>, pgsql-performance@postgresql.org
Date: 2002-10-08T05:44:11Z
Lists: pgsql-hackers, pgsql-performance
On 7 Oct 2002 at 11:21, Tom Lane wrote:

> "Shridhar Daithankar" <shridhar_daithankar@persistent.co.in> writes:
> > I say if it's a char field, there should be no indicator of length as
> > it's not required. Just store those many characters straight ahead..
> 
> Your assumption fails when considering UNICODE or other multibyte
> character encodings.

Correct but is it possible to have real char string when database is not 
unicode or when locale defines size of char, to be exact?

In my case varchar does not make sense as all strings are guaranteed to be of 
defined length. While the argument you have put is correct, it's causing a disk 
space leak, to say so.

Bye
 Shridhar

--
Boucher's Observation:	He who blows his own horn always plays the music	several 
octaves higher than originally written.