Re: BUG #17439: DROP FUNCTION functionName(); drops associated generated column without using CASCADE

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #17439: DROP FUNCTION functionName(); drops associated generated column without using CASCADE
Дата
Msg-id CAKFQuwa10Z27W8dm=-DPokw1_gq9TRqMbggg=_ZwdvNG=CYSRg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #17439: DROP FUNCTION functionName(); drops associated generated column without using CASCADE  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Дерево обсуждения
On Tuesday, March 15, 2022, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Is there any recommendation you would have for mitigation besides not
> dropping functions that may be used by generated columns?

I don't see any good user-level workaround :-(.


Create a dummy view that simply calls the function with null inputs.  That view then will at least enforce the dependency.

David J.
 

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #17439: DROP FUNCTION functionName(); drops associated generated column without using CASCADE
Следующее
От: Peter Geoghegan
Дата:
Сообщение: VACUUM can set pages all-frozen without also setting them all-visible