Horton

Re: Alter or rename enum value

Christophe Pettus <xof@thebuild.com>

View thread View on postgr.es
From: Christophe Pettus <xof@thebuild.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "David G. Johnston" <david.g.johnston@gmail.com>, Matthias Kurz <m.kurz@irregular.at>, Jim Nasby <Jim.Nasby@bluetreble.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2016-03-27T04:43:18Z
Lists: pgsql-hackers 
On Mar 26, 2016, at 7:40 AM, Andrew Dunstan <andrew@dunslane.net> wrote:
> It would be nice if we could find a less broad brush approach to dealing with the issue.

I don't know how doable this is, but could we use the existing mechanism of marking an index invalid if it contains an enum type to which a value was added, and the transaction was rolled back?  For the 90% use case, that would be acceptable, I would expect.

--
-- Christophe Pettus
   xof@thebuild.com

Commits

  1. Relax transactional restrictions on ALTER TYPE ... ADD VALUE (redux).

  2. Partially restore comments discussing enum renumbering hazards.

  3. Allow adding values to an enum type created in the current transaction.