Re: Alter or rename enum value
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Matthias Kurz <m.kurz@irregular.at>, pgsql-hackers@postgresql.org
Date: 2016-03-09T16:58:29Z
Lists: pgsql-hackers
On 03/09/2016 11:07 AM, Tom Lane wrote: > Andrew Dunstan <andrew@dunslane.net> writes: >> On 03/09/2016 09:56 AM, Matthias Kurz wrote: >>> Right now it is not possible to rename an enum value. >>> Are there plans to implement this anytime soon? >> I don't know of any plans, but it would be a useful thing. I agree it >> wouldn't be too hard. The workaround is to do an update on pg_enum >> directly, but proper SQL support would be much nicer. > I have a vague recollection that we discussed this at the time the enum > stuff went in, and there are concurrency issues? Don't recall details > though. > > Rings a vague bell, but should it be any worse than adding new labels? cheers andrew
Commits
-
Relax transactional restrictions on ALTER TYPE ... ADD VALUE (redux).
- 212fab9926b2 12.0 landed
-
Partially restore comments discussing enum renumbering hazards.
- c9e2e2db5c20 9.4.0 cited
-
Allow adding values to an enum type created in the current transaction.
- 7b90469b7176 9.3.0 cited