From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Reducing data type space usage |
Date: | 2006-09-16 13:43:22 |
Message-ID: | 14698.1158414202@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> Weren't you the one that's been going on at great length about how
>> wastefully we store CHAR(1) ? Sure, this has a somewhat restricted
>> use case, but it's about as efficient as we could possibly get within
>> that use case.
> Sure, but are you saying you would have this in addition to do variable sized
> varlena headers?
We could ... but right at the moment I'm thinking this would solve 80%
of the problem with about 1% of the work needed for the varlena change.
So my thought is to do this for 8.3 and then wait a couple releases to
see if the more extensive hack is really needed. Even if we did
eventually install variable-sized varlena headers, this layout would
still be useful for types like inet/cidr.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2006-09-16 14:16:01 | Re: Reducing data type space usage |
Previous Message | Tom Lane | 2006-09-16 13:37:08 | Re: Tiny plpython fix |