New error code to track unsupported contexts

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема New error code to track unsupported contexts
Дата
Msg-id CAB7nPqQ-5NAkHQHh_NOm7FPep37NCiLKwPoJ2Yxb8TDoGgbYYA@mail.gmail.com
обсуждение исходный текст
Ответы Re: New error code to track unsupported contexts  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список pgsql-hackers
Дерево обсуждения 
Hi all,

When pg_event_trigger_dropped_objects is run in a context that is not
the one of an event trigger, currently the error code
ERRCODE_FEATURE_NOT_SUPPORTED is returned. Wouldn't it be better to
have an error to define an out-of-context instead? It seems that it
would be a good thing to have more error verbosity for situations like
the case above. Note that this idea has been mentioned on this ML a
couple of weeks back. In any case, attached is a patch showing the
idea.

Opinions? Is that worth having?
Regards,
--
Michael
Вложения

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

Предыдущее
От: David Rowley
Дата:
Сообщение: Re: Marginal performance improvement: replace bms_first_member loops
Следующее
От: Andres Freund
Дата:
Сообщение: How about a option to disable autovacuum cancellation on lock conflict?