| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | <emre(at)hasegeli(dot)com>, Matthias Kurz <m(dot)kurz(at)irregular(dot)at> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Alter or rename enum value |
| Date: | 2016-09-11 03:05:58 |
| Message-ID: | b942ad05-abae-e183-5d28-f6b66ab21a97@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-09-11 03:08:58 | Re: PoC: Make it possible to disallow WHERE-less UPDATE and DELETE |
| Previous Message | Michael Malis | 2016-09-11 03:02:51 | Merge Join with an Index Optimization |