Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackerspgsql-performancepgsql-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

pgsql-performance by date

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

pgsql-hackers by date

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

pgsql-sql by date

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

pgsql-general by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group