Re: Alter or rename enum value

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Matthias Kurz <m(dot)kurz(at)irregular(dot)at>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Alter or rename enum value
Date: 2016-03-25 02:05:44
Message-ID: 56F49CF8.8050007@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/24/16 2:00 PM, Matthias Kurz wrote:
> ALTER TYPE bogon DROP VALUE 'cat'; -- not implemented in 9.5 but should
> work in future
> ROLLBACK;

Dropping a value is significantly harder because that value could be in use.

I'm certain there's a really good reason adding new values isn't allowed
inside of a transaction. It's probably documented in the code.

To answer your question about "what goes into a release", there's really
no process for that. What goes into a release is what someone was
interested enough in to get community approval for the idea, write the
patch, and shepard the patch through the review process. So if you want
these features added, you need to either: do it yourself, convince
someone else to do it for free, or pay someone to do it for you.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2016-03-25 02:30:00 Re: avg,first,last,median in one query
Previous Message Tom Lane 2016-03-25 00:52:21 Re: Rationalizing code-sharing among src/bin/ directories