| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reducing data type space usage |
| Date: | 2006-09-16 17:08:14 |
| Message-ID: | 450C2F7E.1060006@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> I like this scheme a lot - maximum bang for buck.
>>
>
>
>> Is there any chance we can do it transparently, without exposing new
>> types? It is in effect an implementation detail ISTM, and ideally the
>> user would not need to have any knowledge of it.
>>
>
> Well, they'd have to be separate types, but the parser handling of them
> would be reasonably transparent I think. It would work pretty much
> exactly like the way that CHAR(N) maps to "bpchar" now --- is that
> sufficiently well hidden for your taste?
>
>
>
Yeah, probably. At least to the stage where it's not worth a herculean
effort to overcome.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-09-16 17:17:04 | Re: Foreign keys |
| Previous Message | Tom Lane | 2006-09-16 16:43:19 | Re: index help for uuid datatype |