Postgres Pro
Downloads
Home   >   mailing lists

Re: [pgsql-performance] [GENERAL] Large databases, performance - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [pgsql-performance] [GENERAL] Large databases, performance
Date
Msg-id 23897.1034004117@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] Large databases, performance  ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>)
Responses Re: [pgsql-performance] [GENERAL] Large databases, performance  ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>)
List pgsql-hackers
Tree view 
"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.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Manfred Koizar
Date:
Subject: Re: [GENERAL] Large databases, performance
Next
From: Hans-Jürgen Schönig
Date:
Subject: Re: Table spaces again [was Re: Threaded Sorting]