Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1adgeF-0000vh-D9 for pgsql-hackers@arkaria.postgresql.org; Wed, 09 Mar 2016 16:07:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1adgeE-0000tj-RP for pgsql-hackers@arkaria.postgresql.org; Wed, 09 Mar 2016 16:07:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1adgeE-0000tT-7S for pgsql-hackers@postgresql.org; Wed, 09 Mar 2016 16:07:42 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1adgeB-0002Nb-7p for pgsql-hackers@postgresql.org; Wed, 09 Mar 2016 16:07:41 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u29G7YGm025606; Wed, 9 Mar 2016 11:07:34 -0500 From: Tom Lane To: Andrew Dunstan cc: Matthias Kurz , pgsql-hackers@postgresql.org Subject: Re: Alter or rename enum value In-reply-to: <56E049CC.8010201@dunslane.net> References: <56E049CC.8010201@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Wed, 09 Mar 2016 11:05:32 -0500" Date: Wed, 09 Mar 2016 11:07:34 -0500 Message-ID: <25605.1457539654@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Andrew Dunstan 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. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers