Re: Enum proposal / design - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: Enum proposal / design
Date
Msg-id 20060817171145.GR21363@pervasive.com
Whole thread Raw
In response to Re: Enum proposal / design  (Gregory Stark <gsstark@mit.edu>)
Responses Re: Enum proposal / design
List pgsql-hackers
On Wed, Aug 16, 2006 at 07:21:06PM -0400, Gregory Stark wrote:
> This is the same issue we have with char(n) and numeric(x,y) already. If we
> found a general solution for getting the type name to the enum would it also
> help getting the typmod to char(n) and numeric(x,y)? Would it let us store
> those as fixed sized data types?

Hopefully. It would be great to also have a fixed-width raw/bytea field.
See the recent discussions about adding a guid type, etc.

How about this for a TODO:

* Allow for field widths to be stored in the catalog instead of each tuple
   Data types such as char are usually used when the user knows that a   field will always contain a fixed amount of
data.In these cases,   our char implementation is wasteful, because the varlena header   always contains the same
value.If there was a mechanism to obtain   field widths from the catalog there would be no need to store the   field
widthin each tuple. This would be useful for other types as   well (UUID and ENUM, for example).
 
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Autovacuum on by default?
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] selecting large result sets in psql using