Re: [BUGS] BUG #14825: enum type: unsafe use?

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: [BUGS] BUG #14825: enum type: unsafe use?
Дата
Msg-id 7ca5214d-f981-54e4-c65a-470a87aa665e@2ndQuadrant.com
обсуждение исходный текст
Ответ на Re: [BUGS] BUG #14825: enum type: unsafe use?  ("David E. Wheeler" <david@justatheory.com>)
Ответы Re: [BUGS] BUG #14825: enum type: unsafe use?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs

On 09/25/2017 01:34 PM, David E. Wheeler wrote:
> On Sep 25, 2017, at 10:55, Andrew Dunstan <andrew.dunstan@2ndquadrant.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
transactionthat 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!
 
>


OK, that seems to be the consensus. So let's apply the blacklist patch
and then separately remove the 'created in the same transaction' test.
We'll need to adjust the regression tests and docs accordingly.

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Дилян Палаузов
Дата:
Сообщение: [BUGS] Re: Query planner skipping index depending on DISTINCT parameterorder (2)
Следующее
От: Sebastian Gröbler
Дата:
Сообщение: [BUGS] Segmentation fault mayhem