Re: DROP EXTENSION

Поиск
Список
Период
Сортировка
Искать
От
Michelle Schwan
Тема
Re: DROP EXTENSION
Дата
Msg-id
B9948C5F5585784A98B0F992EC6B2BA8065828EF@otwlxg20.opentext.net
Ответ на
Список
Дерево обсуждения
DROP EXTENSION mschwan@opentext.com
Re: DROP EXTENSION Michael Paquier <michael.paquier@gmail.com>
Re: DROP EXTENSION Alvaro Herrera <alvherre@2ndquadrant.com>
Re: DROP EXTENSION Alvaro Herrera <alvherre@2ndquadrant.com>
Re: DROP EXTENSION Tom Lane <tgl@sss.pgh.pa.us>
Re: DROP EXTENSION Alvaro Herrera <alvherre@2ndquadrant.com>
Re: DROP EXTENSION Michelle Schwan <mschwan@opentext.com>
Re: DROP EXTENSION Tom Lane <tgl@sss.pgh.pa.us>
Ok - I understand!

However, could that be stated in the documentation so that is clear?

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us] 
Sent: Tuesday, June 21, 2016 2:27 PM
To: Alvaro Herrera
Cc: Michael Paquier; Michelle Schwan; pgsql-docs@postgresql.org
Subject: Re: [DOCS] DROP EXTENSION

Alvaro Herrera  writes:
> Right; mschwan wrote private email to indicate that the function in 
> question is:

> CREATE OR REPLACE FUNCTION public.f_unaccent(text)
>   RETURNS text AS
> $$
>   select public.unaccent('public.unaccent', $1) $$
>   LANGUAGE sql IMMUTABLE;

> so when the unaccent extension is dropped, this function remains (of
> course) but it stops working.

Ah, I kind of suspected that: the issue is that we don't analyze function bodies to detect dependencies therein.  In a perfect world we would, but there are daunting obstacles in the way.

			regards, tom lane

В списке pgsql-docs по дате отправления
От: Tom Lane
Дата:
Сообщение: Re: DROP EXTENSION
От: Bruce Momjian
Дата:
FAQ