Re: [PATCH] Alter or rename enum value - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: [PATCH] Alter or rename enum value
Date
Msg-id b942ad05-abae-e183-5d28-f6b66ab21a97@BlueTreble.com
Whole thread Raw
In response to Re: [PATCH] Alter or rename enum value  (Emre Hasegeli <emre@hasegeli.com>)
Responses Re: [PATCH] Alter or rename enum value  (Emre Hasegeli <emre@hasegeli.com>)
Re: [PATCH] Alter or rename enum value  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: Michael Malis
Date:
Subject: Merge Join with an Index Optimization
Next
From: Jim Nasby
Date:
Subject: Re: PoC: Make it possible to disallow WHERE-less UPDATE and DELETE