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

From Bruce Momjian
Subject Re: Enum proposal / design
Date
Msg-id 200608180002.k7I02Wi26998@momjian.us
Whole thread Raw
In response to Re: Enum proposal / design  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Enum proposal / design
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Jim C. Nasby wrote:
> >> If there was a mechanism to obtain
> >> field widths from the catalog there would be no need to store the
> >> field width in each tuple. This would be useful for other types as
> >> well (UUID and ENUM, for example).
> 
> > I don't think there is concensus on adding that.
> 
> Well, it's pie-in-the-sky at the moment because we have no credible
> design for doing it.  Whether any given proposal would get accepted
> would depend on what its downsides were.
> 
> Do we (or should we) have a TODO section for "blue sky research
> ideas"?  I'd not object to putting an item like this in such a
> section.  But for most of the TODO items we have a reasonably clear
> idea of what we're talking about, so this doesn't seem to belong
> in with the rest.

Blue sky ideas just don't seem natural on the TODO list.  Some people
wanted to use a wiki, and maybe it would be good for that.

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: [PATCHES] WIP archive_timeout patch
Next
From: Satoshi Nagayasu
Date:
Subject: Re: pgstattuple extension for indexes