From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Matthias Kurz <m.kurz@irregular.at>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Alter or rename enum value
Date: Wed, 9 Mar 2016 11:58:29 -0500
Message-ID: <56E05635.70908@dunslane.net> (raw)
In-Reply-To: <25605.1457539654@sss.pgh.pa.us>
References: <CAO=2mx6uvgPaPDf-rHqG8=1MZnGyVDMQeh8zS4euRyyg4D35OQ@mail.gmail.com>
<56E049CC.8010201@dunslane.net>
<25605.1457539654@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andrew@dunslane.net, tgl@sss.pgh.pa.us, m.kurz@irregular.at
Subject: Re: Alter or rename enum value
In-Reply-To: <56E05635.70908@dunslane.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox