| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Reducing the overhead of NUMERIC data |
| Date: | 2005-11-01 23:05:21 |
| Message-ID: | 29151.1130886321@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> On Tue, Nov 01, 2005 at 05:40:35PM -0500, Tom Lane wrote:
>> Maybe if we had a few other datatypes that could also use the feature.
>> [ thinks... ] inet/cidr comes to mind but I don't see any others.
>> The case seems a bit weak :-(
> Would varchar(255) fit into that case?
That's attractive at first thought, but not when you stop to consider
that most of the string-datatype support is built around the assumption
that text, varchar, and char share the same underlying representation.
You'd have to write a whole bunch of new code to support such a
datatype.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-11-01 23:15:49 | Re: Reducing the overhead of NUMERIC data |
| Previous Message | Simon Riggs | 2005-11-01 22:59:23 | Re: Reducing the overhead of NUMERIC data |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-11-01 23:15:49 | Re: Reducing the overhead of NUMERIC data |
| Previous Message | Marko Kreen | 2005-11-01 23:04:04 | pgcrypto doc polish |