Re: Enum proposal / design

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(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-17 17:42:20
Message-ID: 17982.1155836540@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2006-08-17 17:43:34 Re: Autovacuum on by default?
Previous Message Peter Eisentraut 2006-08-17 17:41:03 Re: An Idea for planner hints