Re: Enum proposal / design

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Gregory Stark <gsstark(at)mit(dot)edu>, Tom Dunstan <pgsql(at)tomd(dot)cc>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Enum proposal / design
Date: 2006-08-18 00:02:32
Message-ID: 200608180002.k7I02Wi26998@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Satoshi Nagayasu 2006-08-18 00:15:59 Re: pgstattuple extension for indexes
Previous Message Florian G. Pflug 2006-08-18 00:02:30 Re: [PATCHES] WIP archive_timeout patch