Re: [pgsql-performance] Large databases, performance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: shridhar_daithankar(at)persistent(dot)co(dot)in
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-general <pgsql-general(at)postgresql(dot)org>, pgsql-performance(at)postgresql(dot)org
Subject: Re: [pgsql-performance] Large databases, performance
Date: 2002-10-07 15:21:57
Message-ID: 23897.1034004117@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-performance pgsql-sql

"Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Manfred Koizar 2002-10-07 15:22:41 Re: Large databases, performance
Previous Message Tom Lane 2002-10-07 15:06:24 Re: Scale, Normalization, and Table Count

Browse pgsql-hackers by date

  From Date Subject
Next Message Manfred Koizar 2002-10-07 15:22:41 Re: Large databases, performance
Previous Message Tom Lane 2002-10-07 15:14:13 Re: Table spaces again [was Re: Threaded Sorting]

Browse pgsql-performance by date

  From Date Subject
Next Message Manfred Koizar 2002-10-07 15:22:41 Re: Large databases, performance
Previous Message Shridhar Daithankar 2002-10-07 14:39:55 Re: [pgsql-performance] Large databases, performance

Browse pgsql-sql by date

  From Date Subject
Next Message Manfred Koizar 2002-10-07 15:22:41 Re: Large databases, performance
Previous Message Shridhar Daithankar 2002-10-07 14:39:55 Re: [pgsql-performance] Large databases, performance