Re: DROP EXTENSION

From: Michelle Schwan <mschwan(at)opentext(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org>
Subject: Re: DROP EXTENSION
Date: 2016-06-21 18:28:53
Message-ID: B9948C5F5585784A98B0F992EC6B2BA8065828EF@otwlxg20.opentext.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Ok - I understand!

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

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

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> 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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Alvaro Herrera 2016-06-21 18:32:58 Re: DROP EXTENSION
Previous Message Tom Lane 2016-06-21 18:26:49 Re: DROP EXTENSION