| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Decibel!" <decibel(at)decibel(dot)org> |
| Cc: | "Stefan Arentz" <stefan(dot)arentz(at)gmail(dot)com>, <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Speeding up schema changes |
| Date: | 2007-09-19 17:43:57 |
| Message-ID: | 87bqbyim8y.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"Decibel!" <decibel(at)decibel(dot)org> writes:
> On Sep 3, 2007, at 7:26 AM, Gregory Stark wrote:
>> Also, incidentally do you have a good reason to use CHAR instead of varchar
>> or
>> text? char(64) will take 64 bytes (actually 68 bytes in 8.2) even if you
>> don't
>> store anything more in it. text or varchar will take only as many bytes as
>> the
>> data you're storing (plus 4 bytes).
>
> Hrm, do we actually pad before storing? ISTM we should really do that the
> other way around...
Yes we do. And it isn't really fixable either. The problem is the familiar old
problem that in Postgres the typmod is not really part of the type and not
always available when we need it to interpret the datum.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philippe Lang | 2007-09-21 08:25:36 | Re: Table transform query |
| Previous Message | Decibel! | 2007-09-19 15:04:50 | Re: Speeding up schema changes |