| From: | Emre Hasegeli <emre(at)hasegeli(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Matthias Kurz <m(dot)kurz(at)irregular(dot)at>, 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 07:04:55 |
| Message-ID: | CAE2gYzzn-R2kZ2tkg0xRfsZUhfgc=qwStj7ZZeoHO6iTaSMOOg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Why not just disallow dropping a value that's still in use? That's certainly
> what I would prefer to happen by default...
Of course, we should disallow it. That problem is what to do next.
We cannot just remove the value, because it might still be referenced
from the inner nodes of the indexes.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2016-09-11 07:16:04 | Re: Write Ahead Logging for Hash Indexes |
| Previous Message | Amit Kapila | 2016-09-11 05:49:21 | Re: WAL consistency check facility |