Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bFQO1-0003zC-VW for pgsql-docs@arkaria.postgresql.org; Tue, 21 Jun 2016 18:26:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bFQO1-00012C-HO for pgsql-docs@arkaria.postgresql.org; Tue, 21 Jun 2016 18:26:57 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bFQO0-00011v-UG for pgsql-docs@postgresql.org; Tue, 21 Jun 2016 18:26:57 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bFQNy-0000yz-07 for pgsql-docs@postgresql.org; Tue, 21 Jun 2016 18:26:55 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u5LIQnbp012383; Tue, 21 Jun 2016 14:26:49 -0400 From: Tom Lane To: Alvaro Herrera cc: Michael Paquier , mschwan@opentext.com, pgsql-docs@postgresql.org Subject: Re: DROP EXTENSION In-reply-to: <20160621181301.GA91352@alvherre.pgsql> References: <20160621181301.GA91352@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Tue, 21 Jun 2016 14:13:01 -0400" Date: Tue, 21 Jun 2016 14:26:49 -0400 Message-ID: <12382.1466533609@sss.pgh.pa.us> X-Pg-Spam-Score: -1.8 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org 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 -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs