| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christophe Pettus <christophe(dot)pettus(at)pgexperts(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: BUG #14825: enum type: unsafe use? |
| Date: | 2017-09-25 17:34:23 |
| Message-ID: | 40FDB1F3-932D-4912-B4C7-F1E26E331079@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Sep 25, 2017, at 10:55, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
> Let's ask a couple of users who I think are or have been actually
> hurting on this point. Christophe and David, any opinions?
If I understand the issue correctly, I think I’d be fine with requiring ALTER TYPE ADD LABEL to be disallowed in a transaction that also CREATEs the type if it’s not currently possible to reliably tell when an enum was created in a transaction. Once you can do that, then by all means allow it!
My $2.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-09-25 17:36:06 | Re: BUG #14828: Security isn't working |
| Previous Message | Christophe Pettus | 2017-09-25 17:32:08 | Re: BUG #14825: enum type: unsafe use? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2017-09-25 17:38:52 | Re: Built-in plugin for logical decoding output |
| Previous Message | Petr Jelinek | 2017-09-25 17:32:29 | Re: Built-in plugin for logical decoding output |