Horton

Re: [PATCH] Alter or rename enum value

Jim Nasby <jim.nasby@bluetreble.com>

View thread View on postgr.es
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: <emre@hasegeli.com>, Matthias Kurz <m.kurz@irregular.at>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>, Andrew Dunstan <andrew@dunslane.net>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, "David G. Johnston" <david.g.johnston@gmail.com>
Date: 2016-09-11T03:05:58Z
Lists: pgsql-hackers 
On 9/8/16 4:55 AM, Emre Hasegeli wrote:
> The main problem that has been discussed before was the indexes.  One
> way is to tackle with it is to reindex all the tables after the
> operation.  Currently we are doing it when the datatype of indexed
> columns change.  So it should be possible, but very expensive.

Why not just disallow dropping a value that's still in use? That's 
certainly what I would prefer to happen by default...
-- 
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
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461

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.