Re: Datatype sizes; a space and speed issue?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joel Matthew <rees(at)ddcom(dot)co(dot)jp>
Cc: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-general(at)postgresql(dot)org
Subject: Re: Datatype sizes; a space and speed issue?
Date: 2004-06-23 06:17:13
Message-ID: 27699.1087971433@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Joel Matthew <rees(at)ddcom(dot)co(dot)jp> writes:
>> ... the length will be stored first (4 bytes)
>> and the actual content following it

> Section 8.3 of the manual seems to indicate that the actual character
> data is stored in a separate file (background table -- I guess that
> might not be a separate file?) for text, unspecified width char, and
> char fields which exceed the specified length.

We may push very-wide fields out to a separate table ("toast table").
This has nothing to do with whether the field is text, varchar(n),
unspecified varchar, or whatever, but only with the physical size
of the data.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-06-23 06:22:15 Re: Datatype sizes; a space and speed issue?
Previous Message Joel Matthew 2004-06-23 05:54:29 Re: Datatype sizes; a space and speed issue?