Re: WIP: extensible enums - Mailing list pgsql-hackers

From Robert Haas
Subject Re: WIP: extensible enums
Date
Msg-id B3D9A4CF-AC75-451E-8AC5-A767D4C22D23@gmail.com
Whole thread Raw
In response to Re: WIP: extensible enums  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: WIP: extensible enums
List pgsql-hackers
On Nov 12, 2010, at 2:20 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Fri, Nov 12, 2010 at 1:55 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Well, you can rename an item today if you don't mind doing a direct
>>> UPDATE on pg_enum.  I think that's probably sufficient if the demand
>>> only amounts to one or two requests a year.  I'd say leave it off the
>>> TODO list till we see if there's more demand than that.
>
>> I'd say put it on and mark it with an [E].  We could use some more
>> [E]asy items for that list.
>
> We don't need to add marginally-useful features just because they're
> easy.  If it doesn't have a real use-case, the incremental maintenance
> cost of more code is a good reason to reject it.

If we allow users to name objects, we ought to make every effort to also allow renaming them.  In my mind, the only way
renamingis too marginal to be useful is if the feature itself is too marginal to be useful. 

...Robert

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: 8.4-vintage problem in postmaster.c
Next
From: "Joshua D. Drake"
Date:
Subject: Re: WIP: extensible enums