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

Re: Datatype sizes; a space and speed issue?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: Joel Matthew <rees(at)ddcom(dot)co(dot)jp>, pgsql-general(at)postgresql(dot)org
Subject: Re: Datatype sizes; a space and speed issue?
Date: 2004-06-23 05:11:50
Message-ID: 27035.1087967510@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> The difference you cite is for char(N) fields, which are always padded
> with blanks to fill the N chars.

And, again, that's N logical *characters*, not bytes.

We used to have some attempts at optimizing on the assumption that
char(n) fields were physically fixed-width, but we gave it up as a
bad job several major releases back ... it was never more than a
very marginal optimization anyway ...

			regards, tom lane

In response to

Responses

pgsql-general by date

Next:From: Madison KellyDate: 2004-06-23 05:37:03
Subject: Re: Datatype sizes; a space and speed issue?
Previous:From: Tom LaneDate: 2004-06-23 05:01:50
Subject: Re: Parameters from trigger to function.

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