| From: | Gregory Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Gregory Stark <gsstark(at)MIT(dot)EDU>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org, Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Subject: | Re: Fixed length data types issue |
| Date: | 2006-09-08 07:22:26 |
| Message-ID: | 87irjyyg99.fsf@stark.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Gregory Stark wrote:
> > I think we have to find a way to remove the varlena length header
> > entirely for fixed length data types since it's going to be the same
> > for every single record in the table.
>
> But that won't help in the example you posted upthread, because char(N)
> is not fixed-length.
Sure it is because any sane database--certainly any sane database using
char(N)--is in C locale anyways.
In any case if you disagree about that (and you're wrong) then substitute some
other data type. Defining such a data type may be part of the problem that has
to be solved here.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew - Supernews | 2006-09-08 07:40:19 | Re: Fixed length data types issue |
| Previous Message | Peter Eisentraut | 2006-09-08 06:57:12 | Re: Fixed length data types issue |